Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 863ae00a024dc26c057a3edfee672979aa8904b499e5441914da7e3a6991f5a4

Tx prefix hash: b0cae716d7c897494e0698ba7c5c5984deef2cbfa970d1342031b72d47cb8f89
Tx public key: 051385338b25797192fbaa37b3181c5ecdbb1c52960e0c571579abb3839cecb4
Timestamp: 1577524315 Timestamp [UCT]: 2019-12-28 09:11:55 Age [y:d:h:m:s]: 04:338:06:38:13
Block: 33319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131048 RingCT/type: yes/0
Extra: 01051385338b25797192fbaa37b3181c5ecdbb1c52960e0c571579abb3839cecb40211000000054ac5aa02000000000000000000

1 output(s) for total of 475.993671920000 dcy

stealth address amount amount idx
00: fafc8e3289098cd172f0dd2a919a83c6eb88f3517a4395350f984c11cd2f0dde 475.993671920000 55764 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": 33329, "vin": [ { "gen": { "height": 33319 } } ], "vout": [ { "amount": 475993671920, "target": { "key": "fafc8e3289098cd172f0dd2a919a83c6eb88f3517a4395350f984c11cd2f0dde" } } ], "extra": [ 1, 5, 19, 133, 51, 139, 37, 121, 113, 146, 251, 170, 55, 179, 24, 28, 94, 205, 187, 28, 82, 150, 14, 12, 87, 21, 121, 171, 179, 131, 156, 236, 180, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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