Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a08788145fe9d22392ec7fd8ea9ed26c8e27397406b48d49ddccba4d5de3fc0a

Tx prefix hash: 011d6657ccc4a2bd0bb2f7027f0a297286dd2ff88f11de4b1b42142cbfdc09a9
Tx public key: 19fca4b0b2e3b53bad69325523c59f0fd71d009d269249e9b45eeca790194af1
Timestamp: 1704271355 Timestamp [UCT]: 2024-01-03 08:42:35 Age [y:d:h:m:s]: 01:055:01:19:34
Block: 927152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300424 RingCT/type: yes/0
Extra: 0119fca4b0b2e3b53bad69325523c59f0fd71d009d269249e9b45eeca790194af102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 932b63015468e844ad0a4d10647bf8a9ca4c6efa40e93d7916cd298e7cb89763 0.600000000000 1384956 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": 927162, "vin": [ { "gen": { "height": 927152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "932b63015468e844ad0a4d10647bf8a9ca4c6efa40e93d7916cd298e7cb89763" } } ], "extra": [ 1, 25, 252, 164, 176, 178, 227, 181, 59, 173, 105, 50, 85, 35, 197, 159, 15, 215, 29, 0, 157, 38, 146, 73, 233, 180, 94, 236, 167, 144, 25, 74, 241, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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