Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b929d1aabbcd0d2f18d4854005c382b680d1555e474a92d9d06cf6296fc2ea5e

Tx prefix hash: e7d4990bda779d6165177ae7287019be3c779248c957e1b3f7724ee37c2549e2
Tx public key: 9334b967b35fed54f3d35a2132e723f00aaa9d234d3d16dd22ae98a83f5d54fa
Timestamp: 1749466190 Timestamp [UCT]: 2025-06-09 10:49:50 Age [y:d:h:m:s]: 00:157:17:56:08
Block: 1301308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110404 RingCT/type: yes/0
Extra: 019334b967b35fed54f3d35a2132e723f00aaa9d234d3d16dd22ae98a83f5d54fa021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fd48a9364c5e3648da1ab6c1b20698675705c5e979f4a00478a3f5979b8428c 0.600000000000 1788865 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": 1301318, "vin": [ { "gen": { "height": 1301308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fd48a9364c5e3648da1ab6c1b20698675705c5e979f4a00478a3f5979b8428c" } } ], "extra": [ 1, 147, 52, 185, 103, 179, 95, 237, 84, 243, 211, 90, 33, 50, 231, 35, 240, 10, 170, 157, 35, 77, 61, 22, 221, 34, 174, 152, 168, 63, 93, 84, 250, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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