Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5afecc18176e9682329436b717bafc35be5315d422d343b38c56ab0b40ae289e

Tx prefix hash: afac0f74ac28595a58aa8f647414052c0753f3cf6880d31bb4281c5ebc540e78
Tx public key: 8c69a2304f3f8dc6d347627a58bf49513cfd8c19e0581ded37ed1fa7be4eef7c
Timestamp: 1714937728 Timestamp [UCT]: 2024-05-05 19:35:28 Age [y:d:h:m:s]: 00:332:00:19:46
Block: 1015593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237312 RingCT/type: yes/0
Extra: 018c69a2304f3f8dc6d347627a58bf49513cfd8c19e0581ded37ed1fa7be4eef7c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f7747bafdaa56b59cceb367211f72f5a41f8ee5f47c6eaf418cbe69926c0cf 0.600000000000 1479004 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": 1015603, "vin": [ { "gen": { "height": 1015593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f7747bafdaa56b59cceb367211f72f5a41f8ee5f47c6eaf418cbe69926c0cf" } } ], "extra": [ 1, 140, 105, 162, 48, 79, 63, 141, 198, 211, 71, 98, 122, 88, 191, 73, 81, 60, 253, 140, 25, 224, 88, 29, 237, 55, 237, 31, 167, 190, 78, 239, 124, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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