Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f6e95a9c8d834da03e222568dee4f49e8dd0bda664ef7fe88c8f7b105b4d00

Tx prefix hash: a139f93f95c0d0b53042e9092042157ffd03223eba824e938e687100ab567c2a
Tx public key: 24cbae1e438cdef1db09f7e07bbbf7e8d853d3d3338af573a54659196d4e65e0
Timestamp: 1704110645 Timestamp [UCT]: 2024-01-01 12:04:05 Age [y:d:h:m:s]: 01:094:07:01:28
Block: 925813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328505 RingCT/type: yes/0
Extra: 0124cbae1e438cdef1db09f7e07bbbf7e8d853d3d3338af573a54659196d4e65e002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98c2cd3b3174792bdecefbef343afc8836012b268bd3b2592bdefb1f40f6550e 0.600000000000 1383583 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": 925823, "vin": [ { "gen": { "height": 925813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98c2cd3b3174792bdecefbef343afc8836012b268bd3b2592bdefb1f40f6550e" } } ], "extra": [ 1, 36, 203, 174, 30, 67, 140, 222, 241, 219, 9, 247, 224, 123, 187, 247, 232, 216, 83, 211, 211, 51, 138, 245, 115, 165, 70, 89, 25, 109, 78, 101, 224, 2, 17, 0, 0, 0, 3, 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