Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cef0cd2b34ae2ff546bd6ac21053b46defa5e0ae894e42413ccd8b31063b3651

Tx prefix hash: 527a4e78479008d83c84b9f486d0e9859b26d2b86e5ab7cbea90ad041dcf5e82
Tx public key: 328692272a7c467014a2c04a55d8eaa7471b2845ce811e717e3345bb188e11e3
Timestamp: 1762917836 Timestamp [UCT]: 2025-11-12 03:23:56 Age [y:d:h:m:s]: 00:016:03:30:30
Block: 1410240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11561 RingCT/type: yes/0
Extra: 01328692272a7c467014a2c04a55d8eaa7471b2845ce811e717e3345bb188e11e30211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 326968b65be00639c19af436811cd067a840f6486eef7bc65cef271ae15c0806 0.600000000000 1898691 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": 1410250, "vin": [ { "gen": { "height": 1410240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "326968b65be00639c19af436811cd067a840f6486eef7bc65cef271ae15c0806" } } ], "extra": [ 1, 50, 134, 146, 39, 42, 124, 70, 112, 20, 162, 192, 74, 85, 216, 234, 167, 71, 27, 40, 69, 206, 129, 30, 113, 126, 51, 69, 187, 24, 142, 17, 227, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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