Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3649e9c1d5205da353d6ab8854ec05103877afcfeb227d937d6e5c4990b109

Tx prefix hash: eafc33f39a71680ae8967325da79b1310bb568f423645b7f239422246d80e016
Tx public key: 1240d9b56e1b9a3471b0705e1cbb83758611ccd8658fb3c0210e358a4c5137f3
Timestamp: 1684638848 Timestamp [UCT]: 2023-05-21 03:14:08 Age [y:d:h:m:s]: 02:173:16:59:59
Block: 764646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643959 RingCT/type: yes/0
Extra: 011240d9b56e1b9a3471b0705e1cbb83758611ccd8658fb3c0210e358a4c5137f3021100000003faf35c9c000000000000000000

1 output(s) for total of 1.796431096000 dcy

stealth address amount amount idx
00: 0d9b4f88e6d6186741f3bbdc54779ebf676a65beaf99f19f9b3f619a42ada488 1.796431096000 1213589 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": 764656, "vin": [ { "gen": { "height": 764646 } } ], "vout": [ { "amount": 1796431096, "target": { "key": "0d9b4f88e6d6186741f3bbdc54779ebf676a65beaf99f19f9b3f619a42ada488" } } ], "extra": [ 1, 18, 64, 217, 181, 110, 27, 154, 52, 113, 176, 112, 94, 28, 187, 131, 117, 134, 17, 204, 216, 101, 143, 179, 192, 33, 14, 53, 138, 76, 81, 55, 243, 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