Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e28a1fd82d984c1295c09f6409c00c8b50cb013fbc2469200b8f8cc394116f90

Tx prefix hash: 2e042935bfa718eb6dddf80b97272f57a842dcd266284c13c17194be29a6be40
Tx public key: 1f38e413fb3db6b264a7ae8a4f742c29b5098a40a7fbcaa3542e18cc03c71828
Timestamp: 1743386834 Timestamp [UCT]: 2025-03-31 02:07:14 Age [y:d:h:m:s]: 00:280:21:41:01
Block: 1250947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198587 RingCT/type: yes/0
Extra: 011f38e413fb3db6b264a7ae8a4f742c29b5098a40a7fbcaa3542e18cc03c718280211000000051a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf8f5ba42ab210bdbb5ac98901bfcf840c4cd06992eead4e52d9929f431acc59 0.600000000000 1738006 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": 1250957, "vin": [ { "gen": { "height": 1250947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf8f5ba42ab210bdbb5ac98901bfcf840c4cd06992eead4e52d9929f431acc59" } } ], "extra": [ 1, 31, 56, 228, 19, 251, 61, 182, 178, 100, 167, 174, 138, 79, 116, 44, 41, 181, 9, 138, 64, 167, 251, 202, 163, 84, 46, 24, 204, 3, 199, 24, 40, 2, 17, 0, 0, 0, 5, 26, 151, 4, 3, 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