Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57db35449b880065a4b5bba3c113b983f0f934096226b2ad8187ea6becbf5d4c

Tx prefix hash: fbcf5b0db7a1a81bbf7d68ce9c2c572176f77559b6b5e99fe260b8ec5428765f
Tx public key: bf324df5e6f37d678bc5d5b30b5491c30e9ba256ff0717c4cc7d5438a8944bfb
Timestamp: 1754819344 Timestamp [UCT]: 2025-08-10 09:49:04 Age [y:d:h:m:s]: 00:072:09:47:37
Block: 1344074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50911 RingCT/type: yes/0
Extra: 01bf324df5e6f37d678bc5d5b30b5491c30e9ba256ff0717c4cc7d5438a8944bfb02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fa246ddc9c319024efb0d2a965930b326a1a2dbceabbd66963ec83142f0f940 0.600000000000 1831943 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": 1344084, "vin": [ { "gen": { "height": 1344074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fa246ddc9c319024efb0d2a965930b326a1a2dbceabbd66963ec83142f0f940" } } ], "extra": [ 1, 191, 50, 77, 245, 230, 243, 125, 103, 139, 197, 213, 179, 11, 84, 145, 195, 14, 155, 162, 86, 255, 7, 23, 196, 204, 125, 84, 56, 168, 148, 75, 251, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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