Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 272ca0dc9ef0fcd621adf2fb6aa9fd5f07b12fbb1ebf787a5e8989b7e09636c9

Tx prefix hash: 515b8ecda5c3883866de18986490d1b16496e45050ca6b13ac161f7cd894fb1c
Tx public key: 34088d87b0a36ef68efb9908922688a320c93f715f0bccf96e54640d81493bb4
Timestamp: 1729031337 Timestamp [UCT]: 2024-10-15 22:28:57 Age [y:d:h:m:s]: 00:098:15:05:24
Block: 1132441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70447 RingCT/type: yes/0
Extra: 0134088d87b0a36ef68efb9908922688a320c93f715f0bccf96e54640d81493bb4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb7b2a2c22c200c7e36e796d4b4eac59f2beeabf3397c72d5ed286123e1f46eb 0.600000000000 1615356 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": 1132451, "vin": [ { "gen": { "height": 1132441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb7b2a2c22c200c7e36e796d4b4eac59f2beeabf3397c72d5ed286123e1f46eb" } } ], "extra": [ 1, 52, 8, 141, 135, 176, 163, 110, 246, 142, 251, 153, 8, 146, 38, 136, 163, 32, 201, 63, 113, 95, 11, 204, 249, 110, 84, 100, 13, 129, 73, 59, 180, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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