Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cfa3e2a089118a797027b2cd237016bd38a8f102fb212cf4c430129b1547efa

Tx prefix hash: 752dbd6117cd0dec673d6979733036b1c0f672fa6a045a6062d948a8ed36fc0a
Tx public key: d8932146ecc67df7b5fd6ce9015a43bb554231e7b9e56135b6f6bcba9fa365a1
Timestamp: 1734523512 Timestamp [UCT]: 2024-12-18 12:05:12 Age [y:d:h:m:s]: 00:096:23:24:36
Block: 1177881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69057 RingCT/type: yes/0
Extra: 01d8932146ecc67df7b5fd6ce9015a43bb554231e7b9e56135b6f6bcba9fa365a10211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a96aadf0fae72dc9411cb17907f5a83437fe5aeb5f9e1ad11c218709aeb669f1 0.600000000000 1664262 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": 1177891, "vin": [ { "gen": { "height": 1177881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a96aadf0fae72dc9411cb17907f5a83437fe5aeb5f9e1ad11c218709aeb669f1" } } ], "extra": [ 1, 216, 147, 33, 70, 236, 198, 125, 247, 181, 253, 108, 233, 1, 90, 67, 187, 85, 66, 49, 231, 185, 229, 97, 53, 182, 246, 188, 186, 159, 163, 101, 161, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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