Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ac1effb8277ae02d8945ef56c1a6f07a8d52eda45021f35075a439f1d897d9

Tx prefix hash: 0d61d25568f3ba843768e28e4424e2e062903aef50c60c8ca8e5da22cd629aad
Tx public key: a63da785726470a5e81d09457e75b4009ec93a5c618949f665a7edeea54db66d
Timestamp: 1698369706 Timestamp [UCT]: 2023-10-27 01:21:46 Age [y:d:h:m:s]: 01:159:22:57:15
Block: 878449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375317 RingCT/type: yes/0
Extra: 01a63da785726470a5e81d09457e75b4009ec93a5c618949f665a7edeea54db66d0211000000044b8f5122000000000000000000

1 output(s) for total of 0.753934846000 dcy

stealth address amount amount idx
00: 81c71033a18f91c29aa101b60b48531a5b42565cfe6ab35bfb55dc11ff2dc081 0.753934846000 1333893 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": 878459, "vin": [ { "gen": { "height": 878449 } } ], "vout": [ { "amount": 753934846, "target": { "key": "81c71033a18f91c29aa101b60b48531a5b42565cfe6ab35bfb55dc11ff2dc081" } } ], "extra": [ 1, 166, 61, 167, 133, 114, 100, 112, 165, 232, 29, 9, 69, 126, 117, 180, 0, 158, 201, 58, 92, 97, 137, 73, 246, 101, 167, 237, 238, 165, 77, 182, 109, 2, 17, 0, 0, 0, 4, 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