Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a51797514a88927c1a0cd6e58dede7964462f47985f0f255394845d601f11d

Tx prefix hash: c9d1e66b38229dbeda6dccedb53d90ff99c08e38b865d7e9e64193d843b8b207
Tx public key: 0de11bdce5f2c56e3f71f046b362bba40d45578222b5de69cf08c7d0c9453b0f
Timestamp: 1681243807 Timestamp [UCT]: 2023-04-11 20:10:07 Age [y:d:h:m:s]: 02:003:19:51:00
Block: 736481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524896 RingCT/type: yes/0
Extra: 010de11bdce5f2c56e3f71f046b362bba40d45578222b5de69cf08c7d0c9453b0f021100000002b3164c24000000000000000000

1 output(s) for total of 2.227065253000 dcy

stealth address amount amount idx
00: 6791f2bbb8847a1375f905a707146abc68dabb55a2c5b9ebf90cee7465a37c31 2.227065253000 1182918 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": 736491, "vin": [ { "gen": { "height": 736481 } } ], "vout": [ { "amount": 2227065253, "target": { "key": "6791f2bbb8847a1375f905a707146abc68dabb55a2c5b9ebf90cee7465a37c31" } } ], "extra": [ 1, 13, 225, 27, 220, 229, 242, 197, 110, 63, 113, 240, 70, 179, 98, 187, 164, 13, 69, 87, 130, 34, 181, 222, 105, 207, 8, 199, 208, 201, 69, 59, 15, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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