Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcd6ba5f0f3741f62fefea0735c47fa9dc55b972452d9cf56965c7f20feedf23

Tx prefix hash: 0ce918870d3f2c2e460d42351119b39ad640d5b54032dd159b078dd1b0cba7a3
Tx public key: 956abeb8c72d2c786a341d08c789ab2e22d90408c43675983739e28b19fb0fd0
Timestamp: 1749594048 Timestamp [UCT]: 2025-06-10 22:20:48 Age [y:d:h:m:s]: 00:163:10:21:03
Block: 1302354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114471 RingCT/type: yes/0
Extra: 01956abeb8c72d2c786a341d08c789ab2e22d90408c43675983739e28b19fb0fd0021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f05a167d8c4ee0304829c3e26be4e05c3e99af4111f1cee9dc3e2ea5b442fabd 0.600000000000 1789923 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": 1302364, "vin": [ { "gen": { "height": 1302354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f05a167d8c4ee0304829c3e26be4e05c3e99af4111f1cee9dc3e2ea5b442fabd" } } ], "extra": [ 1, 149, 106, 190, 184, 199, 45, 44, 120, 106, 52, 29, 8, 199, 137, 171, 46, 34, 217, 4, 8, 196, 54, 117, 152, 55, 57, 226, 139, 25, 251, 15, 208, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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