Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cac390060e1a9ea6f6dfd16f3679acb0c90401b7c99d03a6775381f301e4e07

Tx prefix hash: af57ef346ad0cc06789fd2346e71a58d5b9cbf036df595bf66389edc3bb2ec54
Tx public key: 0fed2e73821b217f5bb17057ca16d5c587ecfb72177fbcd1ba7863c9cb7738e8
Timestamp: 1718366346 Timestamp [UCT]: 2024-06-14 11:59:06 Age [y:d:h:m:s]: 00:258:21:54:09
Block: 1044021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184979 RingCT/type: yes/0
Extra: 010fed2e73821b217f5bb17057ca16d5c587ecfb72177fbcd1ba7863c9cb7738e80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b91e522eca67f75c305e7ca3c5b931fcc2b06666b652a8d9c134f797985ae459 0.600000000000 1513214 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": 1044031, "vin": [ { "gen": { "height": 1044021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b91e522eca67f75c305e7ca3c5b931fcc2b06666b652a8d9c134f797985ae459" } } ], "extra": [ 1, 15, 237, 46, 115, 130, 27, 33, 127, 91, 177, 112, 87, 202, 22, 213, 197, 135, 236, 251, 114, 23, 127, 188, 209, 186, 120, 99, 201, 203, 119, 56, 232, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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