Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b75cd8c7acda875e3c0f5372c3980b576c4da7a2d97fbb68129549dfbf57e1

Tx prefix hash: 8a4fd466abbb28dea1a5afe383387fed51b58eb10fdc5ff16ab6bf70c7516869
Tx public key: 7026f39610da0a39d72eafa0126fe8c2fc5c36c2c8b5c07102f9ba647e616f62
Timestamp: 1737544492 Timestamp [UCT]: 2025-01-22 11:14:52 Age [y:d:h:m:s]: 00:148:18:33:06
Block: 1202811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106058 RingCT/type: yes/0
Extra: 017026f39610da0a39d72eafa0126fe8c2fc5c36c2c8b5c07102f9ba647e616f62021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c750ac46e4cca7497212ab49c626a426d0366f78f4c4f4296f750086d27a8a82 0.600000000000 1689478 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": 1202821, "vin": [ { "gen": { "height": 1202811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c750ac46e4cca7497212ab49c626a426d0366f78f4c4f4296f750086d27a8a82" } } ], "extra": [ 1, 112, 38, 243, 150, 16, 218, 10, 57, 215, 46, 175, 160, 18, 111, 232, 194, 252, 92, 54, 194, 200, 181, 192, 113, 2, 249, 186, 100, 126, 97, 111, 98, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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