Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e9881cad40be273b230b26e165b408b82ce25d0872e420ca6f8e0ffd92b2b60

Tx prefix hash: 4a10db0aeef53072ac34bd47f5675cba76c79ae85358cd5733638b94eef037e6
Tx public key: f15b673b3361cf3d9a2c3ebfcf76c726591a96f328955f9f89889acd5efa15fd
Timestamp: 1705601972 Timestamp [UCT]: 2024-01-18 18:19:32 Age [y:d:h:m:s]: 01:148:04:24:47
Block: 938168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366967 RingCT/type: yes/0
Extra: 01f15b673b3361cf3d9a2c3ebfcf76c726591a96f328955f9f89889acd5efa15fd02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9401615f1751adb8feb75672d043833d77cb0aa1f4a06b074afcbc4e3f6f0b18 0.600000000000 1396236 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": 938178, "vin": [ { "gen": { "height": 938168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9401615f1751adb8feb75672d043833d77cb0aa1f4a06b074afcbc4e3f6f0b18" } } ], "extra": [ 1, 241, 91, 103, 59, 51, 97, 207, 61, 154, 44, 62, 191, 207, 118, 199, 38, 89, 26, 150, 243, 40, 149, 95, 159, 137, 136, 154, 205, 94, 250, 21, 253, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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