Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bf8f150a20155a18fbaee7ed50c8678cf95832261e34056aab6d32476d26077

Tx prefix hash: 3f67ef4c16db52dba1e98b0bc8c692cd9e4477723aaf6b4e3409627a2c312449
Tx public key: df89d8090ff46a04b8fde5c9127a037926aa644233dc570c44a65e090d9e6a68
Timestamp: 1700626504 Timestamp [UCT]: 2023-11-22 04:15:04 Age [y:d:h:m:s]: 01:147:12:32:56
Block: 896940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366602 RingCT/type: yes/0
Extra: 01df89d8090ff46a04b8fde5c9127a037926aa644233dc570c44a65e090d9e6a6802110000000675e3f0e9000000000000000000

1 output(s) for total of 0.654734808000 dcy

stealth address amount amount idx
00: 4079c545f4809849ec4f567de8953c3a83d89f6f673bb0a2a59c03b332a7a176 0.654734808000 1353287 of 0

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": 896950, "vin": [ { "gen": { "height": 896940 } } ], "vout": [ { "amount": 654734808, "target": { "key": "4079c545f4809849ec4f567de8953c3a83d89f6f673bb0a2a59c03b332a7a176" } } ], "extra": [ 1, 223, 137, 216, 9, 15, 244, 106, 4, 184, 253, 229, 201, 18, 122, 3, 121, 38, 170, 100, 66, 51, 220, 87, 12, 68, 166, 94, 9, 13, 158, 106, 104, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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