Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 620ec5b132b4adbea50e0b313d533a36f8044c0e74c819484ca47297bcde4ae5

Tx prefix hash: 76627c75522fc4a6806243fac475cdd214fb50a629a791e3ec402f6f3ea3f24f
Tx public key: f97770d590f6b44c6c02a59ef9754d4d823b32e4a1d3cab5cffcf0debe13f08b
Timestamp: 1635589320 Timestamp [UCT]: 2021-10-30 10:22:00 Age [y:d:h:m:s]: 03:009:02:18:19
Block: 363568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 784961 RingCT/type: yes/0
Extra: 01f97770d590f6b44c6c02a59ef9754d4d823b32e4a1d3cab5cffcf0debe13f08b0211000000164f792ffd000000000000000000

1 output(s) for total of 38.313223710000 dcy

stealth address amount amount idx
00: 31f03c25059ac6471db1ac4724103a117c7dacc073c16158d125afeb61fcf1d3 38.313223710000 738890 of 0

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": 363578, "vin": [ { "gen": { "height": 363568 } } ], "vout": [ { "amount": 38313223710, "target": { "key": "31f03c25059ac6471db1ac4724103a117c7dacc073c16158d125afeb61fcf1d3" } } ], "extra": [ 1, 249, 119, 112, 213, 144, 246, 180, 76, 108, 2, 165, 158, 249, 117, 77, 77, 130, 59, 50, 228, 161, 211, 202, 181, 207, 252, 240, 222, 190, 19, 240, 139, 2, 17, 0, 0, 0, 22, 79, 121, 47, 253, 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