Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e6320c395d2994e0bb8fd8715a60b6af97b8db159c3836f4b2ef91d7aea3a5

Tx prefix hash: 7c0a67d187cb1412a315cd56b8a7cc5deecbc1dfa30e5ff727833878b23c4bdb
Tx public key: 68b19fe4b0927a9b854c9fbeec26f708d88f2fb60ae46d3156cf284f3d2959a2
Timestamp: 1648051868 Timestamp [UCT]: 2022-03-23 16:11:08 Age [y:d:h:m:s]: 02:360:09:26:17
Block: 464779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776878 RingCT/type: yes/0
Extra: 0168b19fe4b0927a9b854c9fbeec26f708d88f2fb60ae46d3156cf284f3d2959a20211000000015eb576c5000000000000000000

1 output(s) for total of 17.703325054000 dcy

stealth address amount amount idx
00: 6aa1ad3d8fb1328289897ba5e32ce8cc5f24c9aea21d005c252649638dd375b3 17.703325054000 882734 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": 464789, "vin": [ { "gen": { "height": 464779 } } ], "vout": [ { "amount": 17703325054, "target": { "key": "6aa1ad3d8fb1328289897ba5e32ce8cc5f24c9aea21d005c252649638dd375b3" } } ], "extra": [ 1, 104, 177, 159, 228, 176, 146, 122, 155, 133, 76, 159, 190, 236, 38, 247, 8, 216, 143, 47, 182, 10, 228, 109, 49, 86, 207, 40, 79, 61, 41, 89, 162, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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