Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f8a4f8b9f07d563581bf148422f5ca3a0073168dda537cb62e018448cc8d94a

Tx prefix hash: 30c000a5fd2e8db8af665079080e44347b1a6e3b3545695b9909d2e31aa2d223
Tx public key: ecf5a31e6d872661a16e6eca07f6dc23c81c2e60fbe5bc7732d8a3b31c8dcdd9
Timestamp: 1751098225 Timestamp [UCT]: 2025-06-28 08:10:25 Age [y:d:h:m:s]: 00:134:13:54:50
Block: 1314384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94273 RingCT/type: yes/0
Extra: 01ecf5a31e6d872661a16e6eca07f6dc23c81c2e60fbe5bc7732d8a3b31c8dcdd902110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d165267e1d5e8eb8dab55bfc5eef1c1f62d1bd86f99f1e8a87dd50428c87cc4c 0.600000000000 1802031 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": 1314394, "vin": [ { "gen": { "height": 1314384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d165267e1d5e8eb8dab55bfc5eef1c1f62d1bd86f99f1e8a87dd50428c87cc4c" } } ], "extra": [ 1, 236, 245, 163, 30, 109, 135, 38, 97, 161, 110, 110, 202, 7, 246, 220, 35, 200, 28, 46, 96, 251, 229, 188, 119, 50, 216, 163, 179, 28, 141, 205, 217, 2, 17, 0, 0, 0, 8, 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