Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 999d26ce76df56a1dcc6ccf72f4dae58c09593baf45e76e953718a1d9aff11b5

Tx prefix hash: 0cbe7a84e9c37ac77e19785076b52f615d96523775f64a638ab5f13e47cc240b
Tx public key: bc6e08e8fa211e16dda25fa6e7de734625deb37bebc2e3a344ade203693b5bc5
Timestamp: 1698034290 Timestamp [UCT]: 2023-10-23 04:11:30 Age [y:d:h:m:s]: 01:153:09:10:01
Block: 875652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370627 RingCT/type: yes/0
Extra: 01bc6e08e8fa211e16dda25fa6e7de734625deb37bebc2e3a344ade203693b5bc5021100000003faf35c9c000000000000000000

1 output(s) for total of 0.770196326000 dcy

stealth address amount amount idx
00: 3a778b23e94fcb01a9fbdd67f1cce85d63223687a5ccb1c04a4b8006c5dab2c9 0.770196326000 1330916 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": 875662, "vin": [ { "gen": { "height": 875652 } } ], "vout": [ { "amount": 770196326, "target": { "key": "3a778b23e94fcb01a9fbdd67f1cce85d63223687a5ccb1c04a4b8006c5dab2c9" } } ], "extra": [ 1, 188, 110, 8, 232, 250, 33, 30, 22, 221, 162, 95, 166, 231, 222, 115, 70, 37, 222, 179, 123, 235, 194, 227, 163, 68, 173, 226, 3, 105, 59, 91, 197, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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