Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 517554706c5669c026718e2f96a1c3da5f90c56809e0708261af158832c787c2

Tx prefix hash: 7d9821ec792bfdc76d21598f53891f734ad5a0d82de0de8c1ea135d8171491cc
Tx public key: 2e7e65ab2027fee92d32612e8d6d041200f6595f089110fccc3f0a2e52e4dc2d
Timestamp: 1764253917 Timestamp [UCT]: 2025-11-27 14:31:57 Age [y:d:h:m:s]: 00:026:00:15:28
Block: 1421317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18606 RingCT/type: yes/0
Extra: 012e7e65ab2027fee92d32612e8d6d041200f6595f089110fccc3f0a2e52e4dc2d0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cddf5a18474de1e48cf57444ae4a63c8f68a4a20d2ec6ed8698c77de80a6e81 0.600000000000 1909874 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": 1421327, "vin": [ { "gen": { "height": 1421317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cddf5a18474de1e48cf57444ae4a63c8f68a4a20d2ec6ed8698c77de80a6e81" } } ], "extra": [ 1, 46, 126, 101, 171, 32, 39, 254, 233, 45, 50, 97, 46, 141, 109, 4, 18, 0, 246, 89, 95, 8, 145, 16, 252, 204, 63, 10, 46, 82, 228, 220, 45, 2, 17, 0, 0, 0, 1, 78, 123, 252, 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