Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0712e653fb99a654809272d35f771e55bd4ca8a42d2f42277a7910cd3489d4

Tx prefix hash: dc9e4381b25686f25511dea40a554e2f461cd167c82b68979a9ae482f85718c0
Tx public key: 0b0e4f30ce48ae2a0360e6aa2ea3145b0ff5586f9448a931a9fd3cfc0aad993a
Timestamp: 1749423521 Timestamp [UCT]: 2025-06-08 22:58:41 Age [y:d:h:m:s]: 00:166:00:25:40
Block: 1300934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116341 RingCT/type: yes/0
Extra: 010b0e4f30ce48ae2a0360e6aa2ea3145b0ff5586f9448a931a9fd3cfc0aad993a02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e59d644fd6551a5b5e4c13c3b74d6ad7febae21b0eb45ef5aed55e4623e7a983 0.600000000000 1788487 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": 1300944, "vin": [ { "gen": { "height": 1300934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e59d644fd6551a5b5e4c13c3b74d6ad7febae21b0eb45ef5aed55e4623e7a983" } } ], "extra": [ 1, 11, 14, 79, 48, 206, 72, 174, 42, 3, 96, 230, 170, 46, 163, 20, 91, 15, 245, 88, 111, 148, 72, 169, 49, 169, 253, 60, 252, 10, 173, 153, 58, 2, 17, 0, 0, 0, 3, 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