Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ce845a64f85b8c949ae6b9cd8db6d38be71fb0cce3f8a7dabfbdb0110a92721

Tx prefix hash: d1d06571182eb3058c9a9d779c7e57604241163de572084c9385451396d98228
Tx public key: 312e82520f5071ef9e029db9865e6a97f909067c73785396e5cbeb3ec202a6e0
Timestamp: 1738008409 Timestamp [UCT]: 2025-01-27 20:06:49 Age [y:d:h:m:s]: 00:144:05:11:50
Block: 1206463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102960 RingCT/type: yes/0
Extra: 01312e82520f5071ef9e029db9865e6a97f909067c73785396e5cbeb3ec202a6e002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d563e744746e6fc8625e9e21a9c74e2f0d2ec96a43e25e51f756bbe6f5194e4 0.600000000000 1693168 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": 1206473, "vin": [ { "gen": { "height": 1206463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d563e744746e6fc8625e9e21a9c74e2f0d2ec96a43e25e51f756bbe6f5194e4" } } ], "extra": [ 1, 49, 46, 130, 82, 15, 80, 113, 239, 158, 2, 157, 185, 134, 94, 106, 151, 249, 9, 6, 124, 115, 120, 83, 150, 229, 203, 235, 62, 194, 2, 166, 224, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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