Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36f1bd8b70bec3b7a5de3e6294aa6ca7b02c2b469142ead25e9fbf69d1f1f8ef

Tx prefix hash: 2ff7799ba84d477d132bb3ba0e2617972da9e2ae97492b443c92c7d877b07180
Tx public key: 262e27d3b7dbb918b7206ad07a81f3aadbefa4b43d5d7242d849535860c75383
Timestamp: 1733615663 Timestamp [UCT]: 2024-12-07 23:54:23 Age [y:d:h:m:s]: 00:098:23:42:36
Block: 1170339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70545 RingCT/type: yes/0
Extra: 01262e27d3b7dbb918b7206ad07a81f3aadbefa4b43d5d7242d849535860c75383021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f9e530e3125d12900617c55cb5542bde1599e80a3403a65fd10f7701c81c17b 0.600000000000 1656068 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": 1170349, "vin": [ { "gen": { "height": 1170339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f9e530e3125d12900617c55cb5542bde1599e80a3403a65fd10f7701c81c17b" } } ], "extra": [ 1, 38, 46, 39, 211, 183, 219, 185, 24, 183, 32, 106, 208, 122, 129, 243, 170, 219, 239, 164, 180, 61, 93, 114, 66, 216, 73, 83, 88, 96, 199, 83, 131, 2, 17, 0, 0, 0, 3, 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