Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e06d2f256b5acbc9aa8a4830bd51a6917d082e6133d34da838ce80b959ca4851

Tx prefix hash: 66101cca7f2544253adeec2e3236aac5b437963d55df06f02487077e6049cd82
Tx public key: 573fc8026030c4abdcecc15bbeb495620f4b903f64fb3b1c2470dfb0ed354bee
Timestamp: 1704063085 Timestamp [UCT]: 2023-12-31 22:51:25 Age [y:d:h:m:s]: 01:059:21:10:53
Block: 925417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303894 RingCT/type: yes/0
Extra: 01573fc8026030c4abdcecc15bbeb495620f4b903f64fb3b1c2470dfb0ed354bee0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 414a37b4d9c1c8a2b3a6563109fff4f79055ca216fd2fb63debc01b39c935809 0.600000000000 1383179 of 15

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": 925427, "vin": [ { "gen": { "height": 925417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "414a37b4d9c1c8a2b3a6563109fff4f79055ca216fd2fb63debc01b39c935809" } } ], "extra": [ 1, 87, 63, 200, 2, 96, 48, 196, 171, 220, 236, 193, 91, 190, 180, 149, 98, 15, 75, 144, 63, 100, 251, 59, 28, 36, 112, 223, 176, 237, 53, 75, 238, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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