Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba51760b7fe8880d9785ed26632407c681003046410784af43e1df7b6d071846

Tx prefix hash: a8563b2bddd57620b19efdc19590b3f9065858f3000ec7aa63d5b06759e76fb1
Tx public key: eb6b6e3e80f896937c20f213dab8a524e80f27446f3aae8ddd906d28794428ba
Timestamp: 1741206679 Timestamp [UCT]: 2025-03-05 20:31:19 Age [y:d:h:m:s]: 00:094:06:51:05
Block: 1232907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67444 RingCT/type: yes/0
Extra: 01eb6b6e3e80f896937c20f213dab8a524e80f27446f3aae8ddd906d28794428ba0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f77938affa04be0cbd2e23e69d02af726357dfdaea1c5ebd1f15bcf47aefdd19 0.600000000000 1719824 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": 1232917, "vin": [ { "gen": { "height": 1232907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f77938affa04be0cbd2e23e69d02af726357dfdaea1c5ebd1f15bcf47aefdd19" } } ], "extra": [ 1, 235, 107, 110, 62, 128, 248, 150, 147, 124, 32, 242, 19, 218, 184, 165, 36, 232, 15, 39, 68, 111, 58, 174, 141, 221, 144, 109, 40, 121, 68, 40, 186, 2, 17, 0, 0, 0, 6, 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