Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d2aa2e6af00afb9972be83c0b5d29798b263ab12702937a4cb4eec61c350e0d

Tx prefix hash: 917ed908d7c4a7e7bf30d0cb20c59123ee5f7da8aad0d976c9e641cdc5f92ae2
Tx public key: 87714d3a15932549ecb3971ea36b83d54f4fc6d4cf83a0e8f2acb5330bd7c7c2
Timestamp: 1634728753 Timestamp [UCT]: 2021-10-20 11:19:13 Age [y:d:h:m:s]: 03:066:06:20:22
Block: 356767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 825557 RingCT/type: yes/0
Extra: 0187714d3a15932549ecb3971ea36b83d54f4fc6d4cf83a0e8f2acb5330bd7c7c202110000000bf29d7abf000000000000000000

1 output(s) for total of 40.355498909000 dcy

stealth address amount amount idx
00: 33ab4821a039465298bd00a06061bf96ed72d2d1f0b3e73852ddde12fbd14314 40.355498909000 727777 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": 356777, "vin": [ { "gen": { "height": 356767 } } ], "vout": [ { "amount": 40355498909, "target": { "key": "33ab4821a039465298bd00a06061bf96ed72d2d1f0b3e73852ddde12fbd14314" } } ], "extra": [ 1, 135, 113, 77, 58, 21, 147, 37, 73, 236, 179, 151, 30, 163, 107, 131, 213, 79, 79, 198, 212, 207, 131, 160, 232, 242, 172, 181, 51, 11, 215, 199, 194, 2, 17, 0, 0, 0, 11, 242, 157, 122, 191, 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