Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a69f210df9ec75d72d8cfc4c153f379006ca288c0eaaea822c9858e94345c97

Tx prefix hash: 7231aeb3929f4e075187246f14963369d8bf1a1c3965964bf276d97d5f21f267
Tx public key: 0ffa9b60d8cc3520c62e42d56e2ac138a1f6b99a16d78151d1717d522218afa8
Timestamp: 1714216378 Timestamp [UCT]: 2024-04-27 11:12:58 Age [y:d:h:m:s]: 00:339:03:04:10
Block: 1009601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242423 RingCT/type: yes/0
Extra: 010ffa9b60d8cc3520c62e42d56e2ac138a1f6b99a16d78151d1717d522218afa802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28179f24e99ebd3c9b19b647f2cb445ec2a6dbfd41cc3d24b353270826e008c8 0.600000000000 1471321 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": 1009611, "vin": [ { "gen": { "height": 1009601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28179f24e99ebd3c9b19b647f2cb445ec2a6dbfd41cc3d24b353270826e008c8" } } ], "extra": [ 1, 15, 250, 155, 96, 216, 204, 53, 32, 198, 46, 66, 213, 110, 42, 193, 56, 161, 246, 185, 154, 22, 215, 129, 81, 209, 113, 125, 82, 34, 24, 175, 168, 2, 17, 0, 0, 0, 3, 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