Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fa9f71bd5e277fca2009f274e2986e16773ff2a023fb6abcaf423b8a37ef048

Tx prefix hash: 7fb2e3ae928a63a4c7c039effad29bb88b2ac16000dfa4934ee1e9ec079e4efe
Tx public key: 01baf4dfdf62e488f6d88e503cf28900c14e61cca1117ee24bee2b7afe2f83a4
Timestamp: 1695950946 Timestamp [UCT]: 2023-09-29 01:29:06 Age [y:d:h:m:s]: 01:116:18:24:04
Block: 858383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344682 RingCT/type: yes/0
Extra: 0101baf4dfdf62e488f6d88e503cf28900c14e61cca1117ee24bee2b7afe2f83a4021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.878659955000 dcy

stealth address amount amount idx
00: 252341e28ee7f3f073e4f67f9947870ae2912caaa03136939f178acf352b6906 0.878659955000 1312555 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": 858393, "vin": [ { "gen": { "height": 858383 } } ], "vout": [ { "amount": 878659955, "target": { "key": "252341e28ee7f3f073e4f67f9947870ae2912caaa03136939f178acf352b6906" } } ], "extra": [ 1, 1, 186, 244, 223, 223, 98, 228, 136, 246, 216, 142, 80, 60, 242, 137, 0, 193, 78, 97, 204, 161, 17, 126, 226, 75, 238, 43, 122, 254, 47, 131, 164, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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