Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b66de5c893a24787c0d7c168e5f9470b83489bcfe0aab1a6217cb05948b40685

Tx prefix hash: 9ef804feae60ddadcf0a2373dc0b45c01d51ea4f2c174fb7ab6170f124178d8a
Tx public key: e42451eb04409d5f5c64a40ad6abdce67f59bd07e7b414d9061bd8c8ab41cf9b
Timestamp: 1728924087 Timestamp [UCT]: 2024-10-14 16:41:27 Age [y:d:h:m:s]: 00:151:02:23:22
Block: 1131548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107772 RingCT/type: yes/0
Extra: 01e42451eb04409d5f5c64a40ad6abdce67f59bd07e7b414d9061bd8c8ab41cf9b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e2685c522dca746e1664700fd200b2cce61a2dd36b23201cc3b919203590a29 0.600000000000 1614451 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": 1131558, "vin": [ { "gen": { "height": 1131548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e2685c522dca746e1664700fd200b2cce61a2dd36b23201cc3b919203590a29" } } ], "extra": [ 1, 228, 36, 81, 235, 4, 64, 157, 95, 92, 100, 164, 10, 214, 171, 220, 230, 127, 89, 189, 7, 231, 180, 20, 217, 6, 27, 216, 200, 171, 65, 207, 155, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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