Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc344bdb9d8ad0a17c59bf941c21650820ea56f107a29ce1e034d7ba5324ba1d

Tx prefix hash: 7105856998826c3b4255877aa80f40874cbfb4ceaf0fcbe24f603df89f74e0e3
Tx public key: cc9f464af235e6f64d135ffb884b7690d24ca996ff66b32e34a8d64571787c8f
Timestamp: 1630903972 Timestamp [UCT]: 2021-09-06 04:52:52 Age [y:d:h:m:s]: 03:070:23:10:57
Block: 328350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 825643 RingCT/type: yes/0
Extra: 01cc9f464af235e6f64d135ffb884b7690d24ca996ff66b32e34a8d64571787c8f021100000011baa4486c000000000000000000

1 output(s) for total of 50.123408281000 dcy

stealth address amount amount idx
00: 59f12318f3f397b7c1cad44cb6d6c947bc7dc85ba4bc60a21e0aef723288d620 50.123408281000 679645 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": 328360, "vin": [ { "gen": { "height": 328350 } } ], "vout": [ { "amount": 50123408281, "target": { "key": "59f12318f3f397b7c1cad44cb6d6c947bc7dc85ba4bc60a21e0aef723288d620" } } ], "extra": [ 1, 204, 159, 70, 74, 242, 53, 230, 246, 77, 19, 95, 251, 136, 75, 118, 144, 210, 76, 169, 150, 255, 102, 179, 46, 52, 168, 214, 69, 113, 120, 124, 143, 2, 17, 0, 0, 0, 17, 186, 164, 72, 108, 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