Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e672b5ae711dd077fe7ab3c18e086fe259f9cb27e607bd53419b5cbfe2bef9f

Tx prefix hash: 07a552b87200e33f8a97005c8f2b20c3c3e794af8c8df509b22503ee9d1c96d7
Tx public key: fc1a347fcf6f2bfde042223f81fa8bfb30b6c250b518c446a2dc86f08981ca2f
Timestamp: 1724448932 Timestamp [UCT]: 2024-08-23 21:35:32 Age [y:d:h:m:s]: 00:264:21:08:18
Block: 1094457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189177 RingCT/type: yes/0
Extra: 01fc1a347fcf6f2bfde042223f81fa8bfb30b6c250b518c446a2dc86f08981ca2f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a18f7bac4b2997c7f8e5d76aba30c2adbf89a416f557b98bd3ed312c438a7c8e 0.600000000000 1569574 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": 1094467, "vin": [ { "gen": { "height": 1094457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a18f7bac4b2997c7f8e5d76aba30c2adbf89a416f557b98bd3ed312c438a7c8e" } } ], "extra": [ 1, 252, 26, 52, 127, 207, 111, 43, 253, 224, 66, 34, 63, 129, 250, 139, 251, 48, 182, 194, 80, 181, 24, 196, 70, 162, 220, 134, 240, 137, 129, 202, 47, 2, 17, 0, 0, 0, 6, 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