Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279111fbed52057424e063d64fa4313b7e71ef26587f9699368c65d8de409cb7

Tx prefix hash: adff42e06b94e9e16c7b9c72bc15c2241ef24b5f413689e453f38e408f4cff34
Tx public key: 3c2bfa20227dd0bb5de8fae213be74cff2ebb0d1b99eccfbefaddd29578b0401
Timestamp: 1612409171 Timestamp [UCT]: 2021-02-04 03:26:11 Age [y:d:h:m:s]: 04:004:22:09:17
Block: 191608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1022856 RingCT/type: yes/0
Extra: 013c2bfa20227dd0bb5de8fae213be74cff2ebb0d1b99eccfbefaddd29578b040102110000007d4ea414e5000000000000000000

1 output(s) for total of 142.278466425000 dcy

stealth address amount amount idx
00: b502a4d57c461af8b8b9ab5eeb5b0251e659e2bc3f6189b3128db7631e6dfafd 142.278466425000 385372 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": 191618, "vin": [ { "gen": { "height": 191608 } } ], "vout": [ { "amount": 142278466425, "target": { "key": "b502a4d57c461af8b8b9ab5eeb5b0251e659e2bc3f6189b3128db7631e6dfafd" } } ], "extra": [ 1, 60, 43, 250, 32, 34, 125, 208, 187, 93, 232, 250, 226, 19, 190, 116, 207, 242, 235, 176, 209, 185, 158, 204, 251, 239, 173, 221, 41, 87, 139, 4, 1, 2, 17, 0, 0, 0, 125, 78, 164, 20, 229, 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