Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1b1095ada6cd581d959ec53ce454ea71c17e7f3692847fc4fa6685e21dc85c

Tx prefix hash: 2d67bcce9eb94d81f6cac1a3bc817fdc57c258d97c338775525cbde26d847baf
Tx public key: 7263cce09623c6468ec5d88a76e7e7a830f0ce17dcf240b58113ee961cd8f3f8
Timestamp: 1760401365 Timestamp [UCT]: 2025-10-14 00:22:45 Age [y:d:h:m:s]: 00:028:07:48:06
Block: 1389398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20267 RingCT/type: yes/0
Extra: 017263cce09623c6468ec5d88a76e7e7a830f0ce17dcf240b58113ee961cd8f3f8021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7804d1cfd020fd2a818acfff82e56657d5ad0f9bb90ef07111353e4a2c925d89 0.600000000000 1877627 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": 1389408, "vin": [ { "gen": { "height": 1389398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7804d1cfd020fd2a818acfff82e56657d5ad0f9bb90ef07111353e4a2c925d89" } } ], "extra": [ 1, 114, 99, 204, 224, 150, 35, 198, 70, 142, 197, 216, 138, 118, 231, 231, 168, 48, 240, 206, 23, 220, 242, 64, 181, 129, 19, 238, 150, 28, 216, 243, 248, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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