Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 537299d387e7db30c0a2538dc5d92e1a4c2b5dfd7d705f3a7e62b751cf4ea3e7

Tx prefix hash: bb075b20f58e73d40d338ed4ead012c445a85feba93e71f710f22f192dbf8dd5
Tx public key: 47390f9c71f5d176baa53c52227ac34497ecee9d6557c01b1014a02a0ade05e9
Timestamp: 1736461682 Timestamp [UCT]: 2025-01-09 22:28:02 Age [y:d:h:m:s]: 00:072:15:08:15
Block: 1193893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51694 RingCT/type: yes/0
Extra: 0147390f9c71f5d176baa53c52227ac34497ecee9d6557c01b1014a02a0ade05e9021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd4685a1ac6fd1aa5329a0c6e0dd2523c6903c4f6fe9e18f817aa27017793192 0.600000000000 1680458 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": 1193903, "vin": [ { "gen": { "height": 1193893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd4685a1ac6fd1aa5329a0c6e0dd2523c6903c4f6fe9e18f817aa27017793192" } } ], "extra": [ 1, 71, 57, 15, 156, 113, 245, 209, 118, 186, 165, 60, 82, 34, 122, 195, 68, 151, 236, 238, 157, 101, 87, 192, 27, 16, 20, 160, 42, 10, 222, 5, 233, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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