Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71548591a9e946a408b80776d477d8d182a5096f0aa49e8895875c8a1f2c2d7b

Tx prefix hash: eb0f142e621d81221ed8d3782e2ba6b1c1409fae8b3255b0db19ebc3de50cc3e
Tx public key: ca9a14488cca0a1e91b7e8178c1caa8562fec70bc2d7730ae2ce84e0157e3e45
Timestamp: 1758710570 Timestamp [UCT]: 2025-09-24 10:42:50 Age [y:d:h:m:s]: 00:050:18:03:08
Block: 1375371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36341 RingCT/type: yes/0
Extra: 01ca9a14488cca0a1e91b7e8178c1caa8562fec70bc2d7730ae2ce84e0157e3e45021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c761aa818a875a2aa8f2ed30991a1bc6d79bd4408fd40fda6e7e8a6fd25bb16 0.600000000000 1863456 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": 1375381, "vin": [ { "gen": { "height": 1375371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c761aa818a875a2aa8f2ed30991a1bc6d79bd4408fd40fda6e7e8a6fd25bb16" } } ], "extra": [ 1, 202, 154, 20, 72, 140, 202, 10, 30, 145, 183, 232, 23, 140, 28, 170, 133, 98, 254, 199, 11, 194, 215, 115, 10, 226, 206, 132, 224, 21, 126, 62, 69, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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