Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355275f25a061c0b338369919c473cc24bc1930da7136d0e5e8effb5de5639f5

Tx prefix hash: 5a05c0b64651b28edac0b0b50174bb4209740447a743e1c697df9699e58acfcf
Tx public key: 093e959a8b37e60232932ffc42e29496308e07fe94e9d0b47c57af5b78bad0cc
Timestamp: 1722665199 Timestamp [UCT]: 2024-08-03 06:06:39 Age [y:d:h:m:s]: 00:160:09:55:33
Block: 1079652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114758 RingCT/type: yes/0
Extra: 01093e959a8b37e60232932ffc42e29496308e07fe94e9d0b47c57af5b78bad0cc02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21550c0ff3b2b0eba633cd6a8f0f8ebc7f3410704754204d4a1c57e13a5ce681 0.600000000000 1552701 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": 1079662, "vin": [ { "gen": { "height": 1079652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21550c0ff3b2b0eba633cd6a8f0f8ebc7f3410704754204d4a1c57e13a5ce681" } } ], "extra": [ 1, 9, 62, 149, 154, 139, 55, 230, 2, 50, 147, 47, 252, 66, 226, 148, 150, 48, 142, 7, 254, 148, 233, 208, 180, 124, 87, 175, 91, 120, 186, 208, 204, 2, 17, 0, 0, 0, 8, 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