Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d63108969cb519376fa0c01aac68d611eeff9a9b603b0f9ae9be82209bf25bf8

Tx prefix hash: 07828cc5a8cf090f94ca879f175e9400490d613ad78b69be0c45e7628cc22fb8
Tx public key: 0e7de9fd5d0a6e58fa60de112b7f4a0d400df12d4ab7ccf666494e0a0ffead60
Timestamp: 1635610146 Timestamp [UCT]: 2021-10-30 16:09:06 Age [y:d:h:m:s]: 03:135:23:28:11
Block: 363736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 875482 RingCT/type: yes/0
Extra: 010e7de9fd5d0a6e58fa60de112b7f4a0d400df12d4ab7ccf666494e0a0ffead600211000000054a0f5013000000000000000000

1 output(s) for total of 38.264817455000 dcy

stealth address amount amount idx
00: 256f8a31f88bc3c9e56857ea7ee6c4bbabfb89322e0b8a711e238c620b30b89c 38.264817455000 739166 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": 363746, "vin": [ { "gen": { "height": 363736 } } ], "vout": [ { "amount": 38264817455, "target": { "key": "256f8a31f88bc3c9e56857ea7ee6c4bbabfb89322e0b8a711e238c620b30b89c" } } ], "extra": [ 1, 14, 125, 233, 253, 93, 10, 110, 88, 250, 96, 222, 17, 43, 127, 74, 13, 64, 13, 241, 45, 74, 183, 204, 246, 102, 73, 78, 10, 15, 254, 173, 96, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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