Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050f24f90012cf0d4456d0f2e78dfa56ddaf7494e8b532e5885f3d575594a0f0

Tx prefix hash: 57033b355b083f7ca1202cbd8a85bfa7635f2de59dbdd34e78e2b7a98dad4dd2
Tx public key: 1c5588429c3e8d5a9d9e74ed4c5501cc223570567c0a5cbc7ece16a214004891
Timestamp: 1631431637 Timestamp [UCT]: 2021-09-12 07:27:17 Age [y:d:h:m:s]: 03:161:17:50:11
Block: 332158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 890857 RingCT/type: yes/0
Extra: 011c5588429c3e8d5a9d9e74ed4c5501cc223570567c0a5cbc7ece16a21400489102110000000137cb3088000000000000000000

1 output(s) for total of 48.688131057000 dcy

stealth address amount amount idx
00: 0ea425a57b27bf0d494d1bcdb879a4631458f890718e587ad48bfb509054214f 48.688131057000 686051 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": 332168, "vin": [ { "gen": { "height": 332158 } } ], "vout": [ { "amount": 48688131057, "target": { "key": "0ea425a57b27bf0d494d1bcdb879a4631458f890718e587ad48bfb509054214f" } } ], "extra": [ 1, 28, 85, 136, 66, 156, 62, 141, 90, 157, 158, 116, 237, 76, 85, 1, 204, 34, 53, 112, 86, 124, 10, 92, 188, 126, 206, 22, 162, 20, 0, 72, 145, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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