Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47dec5ce6a05567e94a2a4b26cedab042ffcb0f6112d0d37aa70d7fafe37145f

Tx prefix hash: ea0dfad3589a40e535506d2e5e14a3b455e6b15eea6d5d4fc8b17851f545f543
Tx public key: bbe2d12349025c77d4ff03ba1d1606e4798edfb4b1b4969900eec1db8f232145
Timestamp: 1749617926 Timestamp [UCT]: 2025-06-11 04:58:46 Age [y:d:h:m:s]: 00:151:17:06:29
Block: 1302533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106124 RingCT/type: yes/0
Extra: 01bbe2d12349025c77d4ff03ba1d1606e4798edfb4b1b4969900eec1db8f23214502110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25593c281dc574d5f291bd55d0f6a627ac00f34cd08cb6b712fba202b0d97e49 0.600000000000 1790104 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": 1302543, "vin": [ { "gen": { "height": 1302533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25593c281dc574d5f291bd55d0f6a627ac00f34cd08cb6b712fba202b0d97e49" } } ], "extra": [ 1, 187, 226, 209, 35, 73, 2, 92, 119, 212, 255, 3, 186, 29, 22, 6, 228, 121, 142, 223, 180, 177, 180, 150, 153, 0, 238, 193, 219, 143, 35, 33, 69, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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