Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f4ddb7844038cba4916fa22443ef1046f02a0a9a36ae3a700360cb47ef67fd

Tx prefix hash: 565780c6f292ff1010f0d9c3808be4acacf60cce377cb5a10e04db880bb13b2a
Tx public key: 96aa63093990105a008bebc437a7ef894ae96a43edf869194cbc116e06c79e1c
Timestamp: 1696826577 Timestamp [UCT]: 2023-10-09 04:42:57 Age [y:d:h:m:s]: 01:107:08:31:22
Block: 865649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337939 RingCT/type: yes/0
Extra: 0196aa63093990105a008bebc437a7ef894ae96a43edf869194cbc116e06c79e1c0211000000034b8f5122000000000000000000

1 output(s) for total of 0.831276587000 dcy

stealth address amount amount idx
00: 8728d7935aa107d3ad7e41585de1c0b055aa2d8482df2cb29522d9cb208322e0 0.831276587000 1320187 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": 865659, "vin": [ { "gen": { "height": 865649 } } ], "vout": [ { "amount": 831276587, "target": { "key": "8728d7935aa107d3ad7e41585de1c0b055aa2d8482df2cb29522d9cb208322e0" } } ], "extra": [ 1, 150, 170, 99, 9, 57, 144, 16, 90, 0, 139, 235, 196, 55, 167, 239, 137, 74, 233, 106, 67, 237, 248, 105, 25, 76, 188, 17, 110, 6, 199, 158, 28, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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