Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39edfab29bc851d5b7052a0ad12d3a87c258ee1a7ba7e15718be2612c53cdab8

Tx prefix hash: 4d15c1cb285491ef91eab136b559733d07830eee000e4000b81b962849606d73
Tx public key: 979ec32e676f8eb10fa0537b0ec11b2ac5709f8f6350f5f7ac0ca65f1759dc1a
Timestamp: 1719746939 Timestamp [UCT]: 2024-06-30 11:28:59 Age [y:d:h:m:s]: 00:346:15:15:15
Block: 1055449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247711 RingCT/type: yes/0
Extra: 01979ec32e676f8eb10fa0537b0ec11b2ac5709f8f6350f5f7ac0ca65f1759dc1a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30b9c3cbf69ef2941ab1789e7df05bc8c1e1f32e2aeb6e57c91ed866bc0c72f1 0.600000000000 1525850 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": 1055459, "vin": [ { "gen": { "height": 1055449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30b9c3cbf69ef2941ab1789e7df05bc8c1e1f32e2aeb6e57c91ed866bc0c72f1" } } ], "extra": [ 1, 151, 158, 195, 46, 103, 111, 142, 177, 15, 160, 83, 123, 14, 193, 27, 42, 197, 112, 159, 143, 99, 80, 245, 247, 172, 12, 166, 95, 23, 89, 220, 26, 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