Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75386414b68da4f1a9ee09a48d285b59584e1c55fb3659d007cfc83372c5ef3a

Tx prefix hash: 2c30496054626f3d0a2a1b51960341ef49ffc62bbeb53b01693325bcd83ffc91
Tx public key: 74cf14d5c090b0e86be7ffc4114fe3d6f0b0ea73853a2e5df0191f36eddaaede
Timestamp: 1745519830 Timestamp [UCT]: 2025-04-24 18:37:10 Age [y:d:h:m:s]: 00:210:17:25:02
Block: 1268614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148320 RingCT/type: yes/0
Extra: 0174cf14d5c090b0e86be7ffc4114fe3d6f0b0ea73853a2e5df0191f36eddaaede0211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94516a0848805eb3eae37584e01b21ba9497711c98d98c6a6b616b6131b6eb37 0.600000000000 1755845 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": 1268624, "vin": [ { "gen": { "height": 1268614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94516a0848805eb3eae37584e01b21ba9497711c98d98c6a6b616b6131b6eb37" } } ], "extra": [ 1, 116, 207, 20, 213, 192, 144, 176, 232, 107, 231, 255, 196, 17, 79, 227, 214, 240, 176, 234, 115, 133, 58, 46, 93, 240, 25, 31, 54, 237, 218, 174, 222, 2, 17, 0, 0, 0, 2, 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