Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afbf706a234711a85d865e0b255c0fb1e8ea26197d6040af8ef6465999e41d81

Tx prefix hash: 7927aec88a3ae9df021b35d4c36baa8bd76e90dabf4c2db1b9558381839978be
Tx public key: 8c0918a2f4a3732b7a09b9ed1d2b7130f0e44e18f7cb39a13ba548cde1753f34
Timestamp: 1711686910 Timestamp [UCT]: 2024-03-29 04:35:10 Age [y:d:h:m:s]: 01:019:01:42:32
Block: 988645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274594 RingCT/type: yes/0
Extra: 018c0918a2f4a3732b7a09b9ed1d2b7130f0e44e18f7cb39a13ba548cde1753f340211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d377324fb700d8dc3a1b69ddb3b45796815199b3bb9ba28b35aa038a72136ae 0.600000000000 1448926 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": 988655, "vin": [ { "gen": { "height": 988645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d377324fb700d8dc3a1b69ddb3b45796815199b3bb9ba28b35aa038a72136ae" } } ], "extra": [ 1, 140, 9, 24, 162, 244, 163, 115, 43, 122, 9, 185, 237, 29, 43, 113, 48, 240, 228, 78, 24, 247, 203, 57, 161, 59, 165, 72, 205, 225, 117, 63, 52, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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