Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0eadb6fb3cfc6750ff6a2bb7125d1d01942fd1c24eb525b1a9e1a3f3718dc692

Tx prefix hash: b1a2656a8540fca4973fb1a77ad9e4fc115e44bb8ef9cefbf4a7e7a17e4ea772
Tx public key: 65d0fa849e49058d6e9e70f2910d2ece28b4bebaf8f281963644b4f3addd71b6
Timestamp: 1712917545 Timestamp [UCT]: 2024-04-12 10:25:45 Age [y:d:h:m:s]: 01:204:13:59:34
Block: 998810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404892 RingCT/type: yes/0
Extra: 0165d0fa849e49058d6e9e70f2910d2ece28b4bebaf8f281963644b4f3addd71b602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0f5f5996c5df6705abd0a6ae7b8ad7c2ead289ab92c981a72eb903e6976af8 0.600000000000 1459274 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 998820, "vin": [ { "gen": { "height": 998810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0f5f5996c5df6705abd0a6ae7b8ad7c2ead289ab92c981a72eb903e6976af8" } } ], "extra": [ 1, 101, 208, 250, 132, 158, 73, 5, 141, 110, 158, 112, 242, 145, 13, 46, 206, 40, 180, 190, 186, 248, 242, 129, 150, 54, 68, 180, 243, 173, 221, 113, 182, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8