Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2812c06160ebaf5e50f239ce3eba4a14ec19c095bd3f9be2d732f1d84186dc17

Tx prefix hash: aca0d7d5cac039ee359c0a30ad10e7719395f4079fff4910a398ec275f2f7eba
Tx public key: dcf96505fc8e4e1df6d1864f19b9eb30d5189b1751ad3c64a0f7a427b612b757
Timestamp: 1580266817 Timestamp [UCT]: 2020-01-29 03:00:17 Age [y:d:h:m:s]: 05:134:16:00:39
Block: 54621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247629 RingCT/type: yes/0
Extra: 01dcf96505fc8e4e1df6d1864f19b9eb30d5189b1751ad3c64a0f7a427b612b757021100000001ff58ae94000000000000000000

1 output(s) for total of 404.593385996000 dcy

stealth address amount amount idx
00: 846bcb3c99fc77e16c77855b3719ebf2f5cdc04b7be0e003188c5bb5fa5ec7f1 404.593385996000 101065 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": 54631, "vin": [ { "gen": { "height": 54621 } } ], "vout": [ { "amount": 404593385996, "target": { "key": "846bcb3c99fc77e16c77855b3719ebf2f5cdc04b7be0e003188c5bb5fa5ec7f1" } } ], "extra": [ 1, 220, 249, 101, 5, 252, 142, 78, 29, 246, 209, 134, 79, 25, 185, 235, 48, 213, 24, 155, 23, 81, 173, 60, 100, 160, 247, 164, 39, 182, 18, 183, 87, 2, 17, 0, 0, 0, 1, 255, 88, 174, 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