Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4e9160167f724055a8f681b95ff36b4d230664a9bffba61c2c44048c886e66b

Tx prefix hash: 5c1c2f81af7bc3f9026dedd251fb742200a4605f7c33d017f15920a3573e48b3
Tx public key: 76b087c89b6b568031c2776460a6a45efa8ce556c364a62a988b031518796e91
Timestamp: 1737374874 Timestamp [UCT]: 2025-01-20 12:07:54 Age [y:d:h:m:s]: 00:301:09:57:31
Block: 1201406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212968 RingCT/type: yes/0
Extra: 0176b087c89b6b568031c2776460a6a45efa8ce556c364a62a988b031518796e910211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8984d3c40e7ba85a4325cdc01cde4c8d0e41e5cb2c79c74525be03ec6d980ee7 0.600000000000 1688057 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": 1201416, "vin": [ { "gen": { "height": 1201406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8984d3c40e7ba85a4325cdc01cde4c8d0e41e5cb2c79c74525be03ec6d980ee7" } } ], "extra": [ 1, 118, 176, 135, 200, 155, 107, 86, 128, 49, 194, 119, 100, 96, 166, 164, 94, 250, 140, 229, 86, 195, 100, 166, 42, 152, 139, 3, 21, 24, 121, 110, 145, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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