Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f2e86f66f3d0c605891d259fb7d96afd934e6fa0e2cf50b755db36edfb7404

Tx prefix hash: a92b8f0fa9c914ab44783998036ead252ec0b01a871ec5747e71b84e9e7e6938
Tx public key: 41c6c76ae92d75318930e8be6035c9493a652cb45df5e1d4ad3322e87da35001
Timestamp: 1707047522 Timestamp [UCT]: 2024-02-04 11:52:02 Age [y:d:h:m:s]: 00:257:02:43:59
Block: 950160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184188 RingCT/type: yes/0
Extra: 0141c6c76ae92d75318930e8be6035c9493a652cb45df5e1d4ad3322e87da3500102110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 373c3a23b63add4ce98f28f1ebc23f5e6f98f2e0188f0721c3137e05e5489874 0.600000000000 1408730 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": 950170, "vin": [ { "gen": { "height": 950160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "373c3a23b63add4ce98f28f1ebc23f5e6f98f2e0188f0721c3137e05e5489874" } } ], "extra": [ 1, 65, 198, 199, 106, 233, 45, 117, 49, 137, 48, 232, 190, 96, 53, 201, 73, 58, 101, 44, 180, 93, 245, 225, 212, 173, 51, 34, 232, 125, 163, 80, 1, 2, 17, 0, 0, 0, 13, 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