Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ea2493c770e03a191ca22460d9b15a215928138f2c6a2e94b515e6f92e8be24

Tx prefix hash: a393253efb2574045945a236b6af9b36dcdff88943a5094c963438164bf7b54c
Tx public key: eae9bac1b0da03fee6f4efeae1854907720c00a9a6b2a7077aa3ec17bec3c539
Timestamp: 1704602279 Timestamp [UCT]: 2024-01-07 04:37:59 Age [y:d:h:m:s]: 02:002:15:05:07
Block: 929876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521674 RingCT/type: yes/0
Extra: 01eae9bac1b0da03fee6f4efeae1854907720c00a9a6b2a7077aa3ec17bec3c53902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba86fec1cd85ad0e752a46d5d7932e7ddba6481bff435ffa9b8202fcc277acf0 0.600000000000 1387752 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": 929886, "vin": [ { "gen": { "height": 929876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba86fec1cd85ad0e752a46d5d7932e7ddba6481bff435ffa9b8202fcc277acf0" } } ], "extra": [ 1, 234, 233, 186, 193, 176, 218, 3, 254, 230, 244, 239, 234, 225, 133, 73, 7, 114, 12, 0, 169, 166, 178, 167, 7, 122, 163, 236, 23, 190, 195, 197, 57, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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