Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441f7aabcf92b690e140eed607a809c1c24bb52f2e66ad3fab0edf04e362b575

Tx prefix hash: a53bf937850380b32b5bb8f938b7a44691cb5c8575b9a8bc2681712a7addac36
Tx public key: c06a2c28515508e1f7cb274adacd2c04d57a7f705daa62de71212d2c4336e555
Timestamp: 1617050519 Timestamp [UCT]: 2021-03-29 20:41:59 Age [y:d:h:m:s]: 03:316:18:46:20
Block: 229232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 985646 RingCT/type: yes/0
Extra: 01c06a2c28515508e1f7cb274adacd2c04d57a7f705daa62de71212d2c4336e55502110000000c9c1fbdcc000000000000000000

1 output(s) for total of 106.772597472000 dcy

stealth address amount amount idx
00: 9faa0e5ce07252b89719088efab57b9371cf569934210c64fc3aefaccbd5185f 106.772597472000 475606 of 0

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": 229242, "vin": [ { "gen": { "height": 229232 } } ], "vout": [ { "amount": 106772597472, "target": { "key": "9faa0e5ce07252b89719088efab57b9371cf569934210c64fc3aefaccbd5185f" } } ], "extra": [ 1, 192, 106, 44, 40, 81, 85, 8, 225, 247, 203, 39, 74, 218, 205, 44, 4, 213, 122, 127, 112, 93, 170, 98, 222, 113, 33, 45, 44, 67, 54, 229, 85, 2, 17, 0, 0, 0, 12, 156, 31, 189, 204, 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