Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4ccf4b6bb7423b0c3c3ac475cbf38bdb9fe4b8b804f8cbf4376d12843917e5b

Tx prefix hash: cfc135a12793f8613bfe4659d24881b72a55d56ce4ded7e7b4aa4ae062fb74fb
Tx public key: 66992dfd30ff74f995280ec71c60ec8ed37a018d894bf1d8df302cdc0c9eda4a
Timestamp: 1764284056 Timestamp [UCT]: 2025-11-27 22:54:16 Age [y:d:h:m:s]: 00:061:02:12:01
Block: 1421573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43549 RingCT/type: yes/0
Extra: 0166992dfd30ff74f995280ec71c60ec8ed37a018d894bf1d8df302cdc0c9eda4a0211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aa334e352bcda947e469d9fd301d4f5f50371835e64e7ca96952773833c374e 0.600000000000 1910130 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": 1421583, "vin": [ { "gen": { "height": 1421573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aa334e352bcda947e469d9fd301d4f5f50371835e64e7ca96952773833c374e" } } ], "extra": [ 1, 102, 153, 45, 253, 48, 255, 116, 249, 149, 40, 14, 199, 28, 96, 236, 142, 211, 122, 1, 141, 137, 75, 241, 216, 223, 48, 44, 220, 12, 158, 218, 74, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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