Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dc41ae4ce9f7fbad74c04fc3fe07df14e0bc93e96f7b90a26dedea97a3b5e5b

Tx prefix hash: 4c60f7df6135aef6928ddc48c5490d87ad8ef36b2f05941618a3d28a4a954330
Tx public key: e99ae36eee5217836a9695cb59da52d139d1a96c10610655edf9c33ff208b106
Timestamp: 1716939097 Timestamp [UCT]: 2024-05-28 23:31:37 Age [y:d:h:m:s]: 00:228:11:36:32
Block: 1032179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163517 RingCT/type: yes/0
Extra: 01e99ae36eee5217836a9695cb59da52d139d1a96c10610655edf9c33ff208b1060211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4147a275c09eb8572d3c1fe05766856f66ea9617e2aac8d0bd846274be10010f 0.600000000000 1500628 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": 1032189, "vin": [ { "gen": { "height": 1032179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4147a275c09eb8572d3c1fe05766856f66ea9617e2aac8d0bd846274be10010f" } } ], "extra": [ 1, 233, 154, 227, 110, 238, 82, 23, 131, 106, 150, 149, 203, 89, 218, 82, 209, 57, 209, 169, 108, 16, 97, 6, 85, 237, 249, 195, 63, 242, 8, 177, 6, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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