Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96da15ae931e2fe241f1e1571f745d4686765693ba9c411a46d0aa9edd86274a

Tx prefix hash: 1ba9b0f6dfdf6303fef73696f8ed32529f02406a9e3400a4fa6e68e69008e417
Tx public key: 5bf8b0cc7591c8d39beff55b0c9138443104f46ff57d5102d6aa6f701838ac08
Timestamp: 1724482020 Timestamp [UCT]: 2024-08-24 06:47:00 Age [y:d:h:m:s]: 00:152:12:08:09
Block: 1094721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109039 RingCT/type: yes/0
Extra: 015bf8b0cc7591c8d39beff55b0c9138443104f46ff57d5102d6aa6f701838ac0802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f6b3ea94deb0550aad7a20b7bbb8bc0444ad6e380eacad1acf386a9bfd2aaf5 0.600000000000 1569840 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": 1094731, "vin": [ { "gen": { "height": 1094721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f6b3ea94deb0550aad7a20b7bbb8bc0444ad6e380eacad1acf386a9bfd2aaf5" } } ], "extra": [ 1, 91, 248, 176, 204, 117, 145, 200, 211, 155, 239, 245, 91, 12, 145, 56, 68, 49, 4, 244, 111, 245, 125, 81, 2, 214, 170, 111, 112, 24, 56, 172, 8, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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