Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a4f23a5deb3122e8eca46a946307db4a44803344ea7386241b5f2bdcde4c6c0

Tx prefix hash: 0836829a30f04b4e5fadb4d877b1ee3c7b7dfbf0a79adb8c9d2ee3834e0af952
Tx public key: 9204efd91fdea42d81e87e4f4a529364f061560d6dc0799ec3ebe9d5a643709d
Timestamp: 1659387935 Timestamp [UCT]: 2022-08-01 21:05:35 Age [y:d:h:m:s]: 03:092:00:53:19
Block: 556634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 845575 RingCT/type: yes/0
Extra: 019204efd91fdea42d81e87e4f4a529364f061560d6dc0799ec3ebe9d5a643709d02110000000233af99f4000000000000000000

1 output(s) for total of 8.782954053000 dcy

stealth address amount amount idx
00: c4e33a8a03f4c9889b3f6edfedd379126e1dda8a1466897590b8df09aa30e5e3 8.782954053000 988578 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": 556644, "vin": [ { "gen": { "height": 556634 } } ], "vout": [ { "amount": 8782954053, "target": { "key": "c4e33a8a03f4c9889b3f6edfedd379126e1dda8a1466897590b8df09aa30e5e3" } } ], "extra": [ 1, 146, 4, 239, 217, 31, 222, 164, 45, 129, 232, 126, 79, 74, 82, 147, 100, 240, 97, 86, 13, 109, 192, 121, 158, 195, 235, 233, 213, 166, 67, 112, 157, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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