Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9e95d45e75a3dd3ccb982230cded1175054f76f28e9ca346dbac4fb071f114e

Tx prefix hash: 9ebb0c64a6768065893fde47fb71cafc179f4e6c3a23808cef91a81fe2d50467
Tx public key: 6945961c1e45c6f3084e27a4af28aa733c1ce19e15712c6a3d9cbfda67020768
Timestamp: 1735474946 Timestamp [UCT]: 2024-12-29 12:22:26 Age [y:d:h:m:s]: 00:108:07:43:23
Block: 1185716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77216 RingCT/type: yes/0
Extra: 016945961c1e45c6f3084e27a4af28aa733c1ce19e15712c6a3d9cbfda670207680211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2de3b7635a6c0995f214fa3ab74b727e6cf2242f66a6f73c04631952dc15dc9 0.600000000000 1672191 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": 1185726, "vin": [ { "gen": { "height": 1185716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2de3b7635a6c0995f214fa3ab74b727e6cf2242f66a6f73c04631952dc15dc9" } } ], "extra": [ 1, 105, 69, 150, 28, 30, 69, 198, 243, 8, 78, 39, 164, 175, 40, 170, 115, 60, 28, 225, 158, 21, 113, 44, 106, 61, 156, 191, 218, 103, 2, 7, 104, 2, 17, 0, 0, 0, 3, 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