Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f90080dfc06a87ba0b67fbbb5e9fbc35cda98917d1579958b8faa39a4b50874

Tx prefix hash: 22e7c79374bd7ae4de19be200465bbb4edba948543c195c7b682cc0e141203f3
Tx public key: b7d82014525dd0e8ee1d20a4f35facdac0d2d72bbde6540931a0dca942230368
Timestamp: 1635029446 Timestamp [UCT]: 2021-10-23 22:50:46 Age [y:d:h:m:s]: 03:189:06:41:23
Block: 359126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913389 RingCT/type: yes/0
Extra: 01b7d82014525dd0e8ee1d20a4f35facdac0d2d72bbde6540931a0dca9422303680211000000145410958b000000000000000000

1 output(s) for total of 39.633907542000 dcy

stealth address amount amount idx
00: e2b1d96e56429653f8f3f50c8abf476d60c47396e9b1f751acd92de23aa96167 39.633907542000 731445 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": 359136, "vin": [ { "gen": { "height": 359126 } } ], "vout": [ { "amount": 39633907542, "target": { "key": "e2b1d96e56429653f8f3f50c8abf476d60c47396e9b1f751acd92de23aa96167" } } ], "extra": [ 1, 183, 216, 32, 20, 82, 93, 208, 232, 238, 29, 32, 164, 243, 95, 172, 218, 192, 210, 215, 43, 189, 230, 84, 9, 49, 160, 220, 169, 66, 35, 3, 104, 2, 17, 0, 0, 0, 20, 84, 16, 149, 139, 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