Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68dded0eeb3509b4e1b5c52c829448b1173a430625166c5a984ef379a5cd318

Tx prefix hash: 60fd6dcaae1b0e158007524cc3e9ac466d53ba87cd71bc3725ba90cb5b894360
Tx public key: 1bf75561c36f9ee1dcde9450c1b962ed22da0435ec5d65fe997f923e50d2b2ef
Timestamp: 1707614185 Timestamp [UCT]: 2024-02-11 01:16:25 Age [y:d:h:m:s]: 00:315:19:38:07
Block: 954863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226140 RingCT/type: yes/0
Extra: 011bf75561c36f9ee1dcde9450c1b962ed22da0435ec5d65fe997f923e50d2b2ef0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 460d140070ebcf4b7a28404acf4b8c27a4409c3b97084d50c0eacd22b06a6273 0.600000000000 1414145 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": 954873, "vin": [ { "gen": { "height": 954863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "460d140070ebcf4b7a28404acf4b8c27a4409c3b97084d50c0eacd22b06a6273" } } ], "extra": [ 1, 27, 247, 85, 97, 195, 111, 158, 225, 220, 222, 148, 80, 193, 185, 98, 237, 34, 218, 4, 53, 236, 93, 101, 254, 153, 127, 146, 62, 80, 210, 178, 239, 2, 17, 0, 0, 0, 2, 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