Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c1fce67e86f1336d162d9456980a0a5c875ae5e3187fd4b33d04fb53f3a6f6f

Tx prefix hash: b113eedb836e8cb94d09058bdf3d27e23447a7010f7d60eca79c4cf094e50a70
Tx public key: c060d6f0cfacec5bf2bfc4e7a033e8a91ccbd18c461061ebb00b0e276d6f34a1
Timestamp: 1752176547 Timestamp [UCT]: 2025-07-10 19:42:27 Age [y:d:h:m:s]: 00:179:03:54:24
Block: 1322810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126721 RingCT/type: yes/0
Extra: 01c060d6f0cfacec5bf2bfc4e7a033e8a91ccbd18c461061ebb00b0e276d6f34a1021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0b871a12cedb7bb0579a6ab6bc94a9ea6fd7b9805bd3234c940cd05d58e418d 0.600000000000 1810541 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": 1322820, "vin": [ { "gen": { "height": 1322810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0b871a12cedb7bb0579a6ab6bc94a9ea6fd7b9805bd3234c940cd05d58e418d" } } ], "extra": [ 1, 192, 96, 214, 240, 207, 172, 236, 91, 242, 191, 196, 231, 160, 51, 232, 169, 28, 203, 209, 140, 70, 16, 97, 235, 176, 11, 14, 39, 109, 111, 52, 161, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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