Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5bfb50aedc58dbfe2b7099b13f445af175a7bdda8984ad9b001af02427da0ca

Tx prefix hash: ccf32be31690184cc11f9d5130f9c8b541352b7323ea94c94f98feca5fc61c27
Tx public key: 32e8d3ebe1054064651bf08d2dbd302a325b0973dfd6343f4858decec33ee5a4
Timestamp: 1576265794 Timestamp [UCT]: 2019-12-13 19:36:34 Age [y:d:h:m:s]: 04:184:20:36:29
Block: 26410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1017731 RingCT/type: yes/0
Extra: 0132e8d3ebe1054064651bf08d2dbd302a325b0973dfd6343f4858decec33ee5a40211000000014ac5aa02000000000000000000

1 output(s) for total of 501.786305045000 dcy

stealth address amount amount idx
00: 4a0045fb11b20eb82610d74a88496cba3b16162bf71f7d2df66a3adf44a4db84 501.786305045000 43731 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": 26420, "vin": [ { "gen": { "height": 26410 } } ], "vout": [ { "amount": 501786305045, "target": { "key": "4a0045fb11b20eb82610d74a88496cba3b16162bf71f7d2df66a3adf44a4db84" } } ], "extra": [ 1, 50, 232, 211, 235, 225, 5, 64, 100, 101, 27, 240, 141, 45, 189, 48, 42, 50, 91, 9, 115, 223, 214, 52, 63, 72, 88, 222, 206, 195, 62, 229, 164, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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