Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9faddbf537ab5de91647a4d98e4818b45ede9ea501b40921bf2a4e2dc2e9fb58

Tx prefix hash: ba89e0fda04c8f6134c25874ef78391287cf3570bb3abc9ff7404362274749e9
Tx public key: 1ab6be9c8f610d5bb21d63b32f4f877927d28853131e9dea08f76c696549c7bd
Timestamp: 1702336016 Timestamp [UCT]: 2023-12-11 23:06:56 Age [y:d:h:m:s]: 01:344:05:40:34
Block: 911122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504889 RingCT/type: yes/0
Extra: 011ab6be9c8f610d5bb21d63b32f4f877927d28853131e9dea08f76c696549c7bd0211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68d1b8d6ad9c00331093df973e53fe922c26fa1b208d4c8e40de1c1ab62fa2d8 0.600000000000 1368301 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": 911132, "vin": [ { "gen": { "height": 911122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68d1b8d6ad9c00331093df973e53fe922c26fa1b208d4c8e40de1c1ab62fa2d8" } } ], "extra": [ 1, 26, 182, 190, 156, 143, 97, 13, 91, 178, 29, 99, 179, 47, 79, 135, 121, 39, 210, 136, 83, 19, 30, 157, 234, 8, 247, 108, 105, 101, 73, 199, 189, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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