Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4af694d5991e58fec465ff5d7c40a4db2af570b4c557ef9842c05fc393b5a9b

Tx prefix hash: b1f75be6c29b2e951062b8f8cefa91089cd7017f6f1dc8bdc566fe822acd3994
Tx public key: 982ddb9b865538d0004bd776a2261473b06525fbffc9759997e63e82d27f44c9
Timestamp: 1728923025 Timestamp [UCT]: 2024-10-14 16:23:45 Age [y:d:h:m:s]: 00:168:02:39:31
Block: 1131541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119917 RingCT/type: yes/0
Extra: 01982ddb9b865538d0004bd776a2261473b06525fbffc9759997e63e82d27f44c902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5c03576e5e6923c518d23b5880dcca12ed271f99e8d6410a1fdae87ece0c8e9 0.600000000000 1614444 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": 1131551, "vin": [ { "gen": { "height": 1131541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5c03576e5e6923c518d23b5880dcca12ed271f99e8d6410a1fdae87ece0c8e9" } } ], "extra": [ 1, 152, 45, 219, 155, 134, 85, 56, 208, 0, 75, 215, 118, 162, 38, 20, 115, 176, 101, 37, 251, 255, 201, 117, 153, 151, 230, 62, 130, 210, 127, 68, 201, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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