Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e321e308b2839a426edc96fa5453039fb61a227a37ce80d16fe423317d13a0b

Tx prefix hash: edd72ff8c9df0650b7e24a1ec53dbb1863cbb2922b743126149d5bd28be37021
Tx public key: 38cd9ba65a1fb0f81e3f7c1a4a37192b06c0a4ce6fc5d0d01bcdc9707da168c2
Timestamp: 1659307318 Timestamp [UCT]: 2022-07-31 22:41:58 Age [y:d:h:m:s]: 03:099:08:48:46
Block: 555986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 850796 RingCT/type: yes/0
Extra: 0138cd9ba65a1fb0f81e3f7c1a4a37192b06c0a4ce6fc5d0d01bcdc9707da168c202110000000b6570b1ef000000000000000000

1 output(s) for total of 8.826483318000 dcy

stealth address amount amount idx
00: cf1be0294d19a92795545656e7cefb1deeabb3d825db71fb4e5dcbf9a8aeb734 8.826483318000 987906 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": 555996, "vin": [ { "gen": { "height": 555986 } } ], "vout": [ { "amount": 8826483318, "target": { "key": "cf1be0294d19a92795545656e7cefb1deeabb3d825db71fb4e5dcbf9a8aeb734" } } ], "extra": [ 1, 56, 205, 155, 166, 90, 31, 176, 248, 30, 63, 124, 26, 74, 55, 25, 43, 6, 192, 164, 206, 111, 197, 208, 208, 27, 205, 201, 112, 125, 161, 104, 194, 2, 17, 0, 0, 0, 11, 101, 112, 177, 239, 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