Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb9888d512ea89cd2c7efbc40fa6fd187ceab89a0362e866a4f83a384ba8ebcc

Tx prefix hash: 777bc41166ac9639164f1b17865d0e40859df833d6bd988baabde993785d2874
Tx public key: 176df4973fee1f136d4dffe902d2d3ab962654769fb03caec49e95ee66d7b727
Timestamp: 1717861420 Timestamp [UCT]: 2024-06-08 15:43:40 Age [y:d:h:m:s]: 00:302:12:53:17
Block: 1039830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216192 RingCT/type: yes/0
Extra: 01176df4973fee1f136d4dffe902d2d3ab962654769fb03caec49e95ee66d7b72702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8310f258bb93a761e1b2d5a906452a1da455f8e2d6ab5f70a7e4ce7b03fb5a65 0.600000000000 1508485 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": 1039840, "vin": [ { "gen": { "height": 1039830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8310f258bb93a761e1b2d5a906452a1da455f8e2d6ab5f70a7e4ce7b03fb5a65" } } ], "extra": [ 1, 23, 109, 244, 151, 63, 238, 31, 19, 109, 77, 255, 233, 2, 210, 211, 171, 150, 38, 84, 118, 159, 176, 60, 174, 196, 158, 149, 238, 102, 215, 183, 39, 2, 17, 0, 0, 0, 3, 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