Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed45bb7069c933aa70abf201a90f3a66b9cbccd6fae2048c7b626d45b89359a4

Tx prefix hash: 5e50c1776588a516b3839691a36f8a511bfbc38c061f01d45ecc3140d09ffdee
Tx public key: 44cc73a9b543322aa2d3b82d11bd8dbe5bf834564a5dda61b0284b093d525b61
Timestamp: 1712395159 Timestamp [UCT]: 2024-04-06 09:19:19 Age [y:d:h:m:s]: 00:266:21:26:45
Block: 994479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191069 RingCT/type: yes/0
Extra: 0144cc73a9b543322aa2d3b82d11bd8dbe5bf834564a5dda61b0284b093d525b6102110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e36703c1b99341e4257591f40d501c653dae94e182bdce7629a5708a56713ee 0.600000000000 1454881 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": 994489, "vin": [ { "gen": { "height": 994479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e36703c1b99341e4257591f40d501c653dae94e182bdce7629a5708a56713ee" } } ], "extra": [ 1, 68, 204, 115, 169, 181, 67, 50, 42, 162, 211, 184, 45, 17, 189, 141, 190, 91, 248, 52, 86, 74, 93, 218, 97, 176, 40, 75, 9, 61, 82, 91, 97, 2, 17, 0, 0, 0, 12, 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