Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62024dc3a17f74eb88c9cb8eaaa68da5298fe5a8153de1aec958bf28c03518c3

Tx prefix hash: 3152ae2dd8827e2ee2d9774a5396ce1ea1870ba0e55eb869b873bef153f136d2
Tx public key: e266c538ec07323666f1ebd84e0de72396d066a5280b8f407c45bc9e7a387724
Timestamp: 1736486612 Timestamp [UCT]: 2025-01-10 05:23:32 Age [y:d:h:m:s]: 00:158:20:51:42
Block: 1194101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113254 RingCT/type: yes/0
Extra: 01e266c538ec07323666f1ebd84e0de72396d066a5280b8f407c45bc9e7a38772402110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60dbac2c589cc1692c7b442151e01392ad17eee1af7538959f826a8a1e3f09ee 0.600000000000 1680668 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": 1194111, "vin": [ { "gen": { "height": 1194101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60dbac2c589cc1692c7b442151e01392ad17eee1af7538959f826a8a1e3f09ee" } } ], "extra": [ 1, 226, 102, 197, 56, 236, 7, 50, 54, 102, 241, 235, 216, 78, 13, 231, 35, 150, 208, 102, 165, 40, 11, 143, 64, 124, 69, 188, 158, 122, 56, 119, 36, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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