Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b32640df24564951f376182bad92651410d6655051723ed48893997c4bb6597

Tx prefix hash: 7613e579b89aa1b5e6fe8cef9eecb6d31412009b49e83c2357d8af1a6fc57cc5
Tx public key: 04e1a7a91ecbe46972cac6d04d958a521ffbb33ed9da5e51a8ad4aaf3b1fa695
Timestamp: 1748928674 Timestamp [UCT]: 2025-06-03 05:31:14 Age [y:d:h:m:s]: 00:170:16:55:30
Block: 1296841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119689 RingCT/type: yes/0
Extra: 0104e1a7a91ecbe46972cac6d04d958a521ffbb33ed9da5e51a8ad4aaf3b1fa695021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 495a0a9fea154e49a065348843c9e88446b2bea404679f13e19817b7e729a21c 0.600000000000 1784358 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": 1296851, "vin": [ { "gen": { "height": 1296841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "495a0a9fea154e49a065348843c9e88446b2bea404679f13e19817b7e729a21c" } } ], "extra": [ 1, 4, 225, 167, 169, 30, 203, 228, 105, 114, 202, 198, 208, 77, 149, 138, 82, 31, 251, 179, 62, 217, 218, 94, 81, 168, 173, 74, 175, 59, 31, 166, 149, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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