Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ed7b5b1d8e70f66c9b917fd55ac1c0ed344fc18c2fc35279d293cf323f69501

Tx prefix hash: bb3d35645cfca4b95511ea47d63f056dba3499f479cd930f062a19151def1b0f
Tx public key: c25b5de6de3746eb3047bd98398d0e609f04cd1cae2a9797988afd2eba20d90c
Timestamp: 1674647006 Timestamp [UCT]: 2023-01-25 11:43:26 Age [y:d:h:m:s]: 02:312:19:07:12
Block: 682433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742949 RingCT/type: yes/0
Extra: 01c25b5de6de3746eb3047bd98398d0e609f04cd1cae2a9797988afd2eba20d90c0211000000015029cbac000000000000000000

1 output(s) for total of 3.363691197000 dcy

stealth address amount amount idx
00: df181cad87ef3fc5a3757d486a1fa2f1751aa207a4378d6ed2ca970ad6e5d6c7 3.363691197000 1124554 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": 682443, "vin": [ { "gen": { "height": 682433 } } ], "vout": [ { "amount": 3363691197, "target": { "key": "df181cad87ef3fc5a3757d486a1fa2f1751aa207a4378d6ed2ca970ad6e5d6c7" } } ], "extra": [ 1, 194, 91, 93, 230, 222, 55, 70, 235, 48, 71, 189, 152, 57, 141, 14, 96, 159, 4, 205, 28, 174, 42, 151, 151, 152, 138, 253, 46, 186, 32, 217, 12, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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