Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bed4b441dbb7ba1dd1de3fd02dc5508a1b498d928d05cce0bdeff8b9e6ba5c2

Tx prefix hash: 51108e4589ad1864aea6db632b6d48b0c34949ecf0e9b071b8f8eccf40e7b7eb
Tx public key: 5b52c27396f22a6c74b370b8aecea4c93d5060220824e58be73077204f08497f
Timestamp: 1745186099 Timestamp [UCT]: 2025-04-20 21:54:59 Age [y:d:h:m:s]: 00:255:00:18:06
Block: 1265842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180042 RingCT/type: yes/0
Extra: 015b52c27396f22a6c74b370b8aecea4c93d5060220824e58be73077204f08497f0211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75f61af080afcfae59053a16782a2eed39ec77e36ed5cfc1bfbfc47595014fdb 0.600000000000 1753055 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": 1265852, "vin": [ { "gen": { "height": 1265842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75f61af080afcfae59053a16782a2eed39ec77e36ed5cfc1bfbfc47595014fdb" } } ], "extra": [ 1, 91, 82, 194, 115, 150, 242, 42, 108, 116, 179, 112, 184, 174, 206, 164, 201, 61, 80, 96, 34, 8, 36, 229, 139, 231, 48, 119, 32, 79, 8, 73, 127, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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