Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc189c6593497c3842ecf4829ca6a261b93e71dd191f53f4b922eb3ea32808cc

Tx prefix hash: 402a3cf2bc0a60b459f3f1e4c67ef859700f45433ead2e04a1cc8d60f0c0663f
Tx public key: 3416d49ba6429d9a8cae49b27347ce589db9582d7d582467fb6d6f130f59b094
Timestamp: 1717382504 Timestamp [UCT]: 2024-06-03 02:41:44 Age [y:d:h:m:s]: 00:346:14:38:15
Block: 1035866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247730 RingCT/type: yes/0
Extra: 013416d49ba6429d9a8cae49b27347ce589db9582d7d582467fb6d6f130f59b094021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69f9ebdfce1d35c8c77a28a790d327dca8e87acc6e9baddc58ccbd84f000ceba 0.600000000000 1504389 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": 1035876, "vin": [ { "gen": { "height": 1035866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69f9ebdfce1d35c8c77a28a790d327dca8e87acc6e9baddc58ccbd84f000ceba" } } ], "extra": [ 1, 52, 22, 212, 155, 166, 66, 157, 154, 140, 174, 73, 178, 115, 71, 206, 88, 157, 185, 88, 45, 125, 88, 36, 103, 251, 109, 111, 19, 15, 89, 176, 148, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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