Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7924557a9c9f117b52c57d469d51468fcc29d3fc8ae6f26314f5b133acfa3c62

Tx prefix hash: 130f2e0d0538d338e6193a4588ef481e6554d5370f9921f400a88b889a89ffa7
Tx public key: 0c1f7eda24b78d816884ca2d41b04c70aab54f94c110dd0e5b57e6e2742958c1
Timestamp: 1711931866 Timestamp [UCT]: 2024-04-01 00:37:46 Age [y:d:h:m:s]: 01:221:07:19:54
Block: 990680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416835 RingCT/type: yes/0
Extra: 010c1f7eda24b78d816884ca2d41b04c70aab54f94c110dd0e5b57e6e2742958c102110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 731425a8d9390ccde8a29f1c5710b2dce5d773d52cbdb92ae404afec97d10b47 0.600000000000 1451006 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": 990690, "vin": [ { "gen": { "height": 990680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "731425a8d9390ccde8a29f1c5710b2dce5d773d52cbdb92ae404afec97d10b47" } } ], "extra": [ 1, 12, 31, 126, 218, 36, 183, 141, 129, 104, 132, 202, 45, 65, 176, 76, 112, 170, 181, 79, 148, 193, 16, 221, 14, 91, 87, 230, 226, 116, 41, 88, 193, 2, 17, 0, 0, 0, 7, 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