Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705a13decd59d2716863e3a7e8f46b5f61ccbe5797c73764616282428ac20ce1

Tx prefix hash: 48e432a928320622b2ce6428148828e76c80964e5bdffc7f727e18e5b3460246
Tx public key: 851780f376055b30a545528a4e98fb909f7e058697893f75df6aaa9faf5fe35c
Timestamp: 1752025914 Timestamp [UCT]: 2025-07-09 01:51:54 Age [y:d:h:m:s]: 00:132:21:22:43
Block: 1321656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93469 RingCT/type: yes/0
Extra: 01851780f376055b30a545528a4e98fb909f7e058697893f75df6aaa9faf5fe35c021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c397cbf3b2ac7ea8d2d96794384a4221cec8b29e9c228769fc4a3e7fdf6ab926 0.600000000000 1809363 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": 1321666, "vin": [ { "gen": { "height": 1321656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c397cbf3b2ac7ea8d2d96794384a4221cec8b29e9c228769fc4a3e7fdf6ab926" } } ], "extra": [ 1, 133, 23, 128, 243, 118, 5, 91, 48, 165, 69, 82, 138, 78, 152, 251, 144, 159, 126, 5, 134, 151, 137, 63, 117, 223, 106, 170, 159, 175, 95, 227, 92, 2, 17, 0, 0, 0, 6, 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