Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5321d842f17045d0bdca048edff5973e9e3b5d4a0f7a45ab00aaa9c6c18fafce

Tx prefix hash: 1a2f72fbfc6fdf37e08d379f97c4da253ef83f5fdc9d79d1d7494e6c92ff7019
Tx public key: cfc27413118fa2e39dd6d35fdb6ae0734eacb244af3eafab4ff255334940703f
Timestamp: 1761821657 Timestamp [UCT]: 2025-10-30 10:54:17 Age [y:d:h:m:s]: 00:070:04:31:57
Block: 1401175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50241 RingCT/type: yes/0
Extra: 01cfc27413118fa2e39dd6d35fdb6ae0734eacb244af3eafab4ff255334940703f021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac2a02a5df47d46dfa1cd11e53a33edf270153d0a5a05097015854300363e1e8 0.600000000000 1889494 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": 1401185, "vin": [ { "gen": { "height": 1401175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac2a02a5df47d46dfa1cd11e53a33edf270153d0a5a05097015854300363e1e8" } } ], "extra": [ 1, 207, 194, 116, 19, 17, 143, 162, 227, 157, 214, 211, 95, 219, 106, 224, 115, 78, 172, 178, 68, 175, 62, 175, 171, 79, 242, 85, 51, 73, 64, 112, 63, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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