Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a97219f1a70567aec87e228c44ed8beac4322ef51c99d06f296251a26df40dc1

Tx prefix hash: 8cdd20dcb7c9159880706e1b13e189c7142f94135816d47c10591e731af11d8c
Tx public key: dfecc5e3c10e7076341de9a5a04853d317e67de9d864c87af77166d13340e57a
Timestamp: 1705505343 Timestamp [UCT]: 2024-01-17 15:29:03 Age [y:d:h:m:s]: 01:068:21:45:40
Block: 937371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310331 RingCT/type: yes/0
Extra: 01dfecc5e3c10e7076341de9a5a04853d317e67de9d864c87af77166d13340e57a0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 509f7e13182c9b54ab0f23d42fdaf3fd45522582b9d31a871e49b5f5d19bdacb 0.600000000000 1395423 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": 937381, "vin": [ { "gen": { "height": 937371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "509f7e13182c9b54ab0f23d42fdaf3fd45522582b9d31a871e49b5f5d19bdacb" } } ], "extra": [ 1, 223, 236, 197, 227, 193, 14, 112, 118, 52, 29, 233, 165, 160, 72, 83, 211, 23, 230, 125, 233, 216, 100, 200, 122, 247, 113, 102, 209, 51, 64, 229, 122, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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