Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd85b93415a1f12a9a3e2cd129cbc211d527a926c325826c0552682cdfd54fce

Tx prefix hash: e3ceb8f15a7d1f18d3ffcede3107a94edab291ef06d06d490e857d8318d45374
Tx public key: 3723239fe51e9aa903405aeae22f640dbc209dc89f63302be9dfb8b10708a012
Timestamp: 1711081444 Timestamp [UCT]: 2024-03-22 04:24:04 Age [y:d:h:m:s]: 00:358:02:26:29
Block: 983638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256035 RingCT/type: yes/0
Extra: 013723239fe51e9aa903405aeae22f640dbc209dc89f63302be9dfb8b10708a01202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7dd067fffb69d05a60d0e274d03645889ea0646089df3e8b2803cf321788bed 0.600000000000 1443779 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": 983648, "vin": [ { "gen": { "height": 983638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7dd067fffb69d05a60d0e274d03645889ea0646089df3e8b2803cf321788bed" } } ], "extra": [ 1, 55, 35, 35, 159, 229, 30, 154, 169, 3, 64, 90, 234, 226, 47, 100, 13, 188, 32, 157, 200, 159, 99, 48, 43, 233, 223, 184, 177, 7, 8, 160, 18, 2, 17, 0, 0, 0, 1, 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