Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c69ad35da3d2af7c024b9781f8390b79bfc2a25e1904a30abe37ae50167878

Tx prefix hash: 6a24144db22d01c82df6680daa1f78e7107c4dadda82d7c9005324f926cf03d7
Tx public key: 5b49e78b43e0db2aa0af0af84c88bbd4e647e2ca91124bcd7e210bf7d9840220
Timestamp: 1715358981 Timestamp [UCT]: 2024-05-10 16:36:21 Age [y:d:h:m:s]: 00:245:03:26:17
Block: 1019077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175456 RingCT/type: yes/0
Extra: 015b49e78b43e0db2aa0af0af84c88bbd4e647e2ca91124bcd7e210bf7d98402200211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d753c433d50de9049ddd5dcbe29f2b05c0b714c087fa1df801b1a645f2af5007 0.600000000000 1482950 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": 1019087, "vin": [ { "gen": { "height": 1019077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d753c433d50de9049ddd5dcbe29f2b05c0b714c087fa1df801b1a645f2af5007" } } ], "extra": [ 1, 91, 73, 231, 139, 67, 224, 219, 42, 160, 175, 10, 248, 76, 136, 187, 212, 230, 71, 226, 202, 145, 18, 75, 205, 126, 33, 11, 247, 217, 132, 2, 32, 2, 17, 0, 0, 0, 3, 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