Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bccb576459b1ed1868416b18de30cb99892ad051780d29989c42e9adc940545

Tx prefix hash: 78a46946110bff017e60118ae3f49d4bafb8dd441a5528594d951dcdc0f2c24e
Tx public key: d3e165f6ade2ea15f2b2e6e57388b5c949212a179e589f5f5c02323d6135c77c
Timestamp: 1710156129 Timestamp [UCT]: 2024-03-11 11:22:09 Age [y:d:h:m:s]: 01:237:19:13:20
Block: 975960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428650 RingCT/type: yes/0
Extra: 01d3e165f6ade2ea15f2b2e6e57388b5c949212a179e589f5f5c02323d6135c77c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dafeb117401eaa3598f7946a61cc14dee044309a1810d60652d64f960efa7a9 0.600000000000 1435939 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": 975970, "vin": [ { "gen": { "height": 975960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dafeb117401eaa3598f7946a61cc14dee044309a1810d60652d64f960efa7a9" } } ], "extra": [ 1, 211, 225, 101, 246, 173, 226, 234, 21, 242, 178, 230, 229, 115, 136, 181, 201, 73, 33, 42, 23, 158, 88, 159, 95, 92, 2, 50, 61, 97, 53, 199, 124, 2, 17, 0, 0, 0, 4, 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